That required quite a lot of steps (Search & Replace actions in MS Word). The result in CafeTran is:
This situation was annoying me. In a brainwave I had the idea to replace all non-breaking spaces in the MS Word document with new line characters (^s with ^l), and hurray: all HTML list items are segmented perfectly without any CafeTran tags!!!
I translated some segments with list items and exported:
Once I have finished this project, I'll have to:
Syncing with PDF from the Studio project:
Would be nice if CafeTran Espresso 10 Croissant had a regular expression tagger.
> Would be nice if CafeTran Espresso 10 Croissant had a regular expression tagger.
I like the way you handled it outside the program but do you realize how complex (and possibly frustrating) the whole issue of custom tagging via the regular expressions might be for most users?
>I like the way you handled it outside the program but do you realize how complex (and possibly frustrating) the whole issue of custom tagging via the regular expressions might be for most users?
Yes, I do. But, OTOH, users come in all flavours. This is still one of very few features that I'm missing often. Most likely because I'm a translator of machine/plant related texts.
CafeTran's insertion of the correct numbers in Fuzzy Matches isn't what it should be ...
I should have masked all isolated numbers for this big job.
>custom tagging via the regular expressions might be for most users?
It would be great if CafeTran Espresso 10 Croissant would have a button in the Add Term dialogue box to convert the selection of the target language box (sic) to regular expressions.
Of course, not everything can be covered. But I guess a 90 % should be feasible. I'm happy to contribute m non-translatables glossaries and mark-up macros for inspiration.
Beware: MS Word removes the HTML formatting for bold and italics!
The whole workflow has worked, except for about 2K words that I have to restore from TM and where I have to insert the HTML formatting for bold and italics. Of course, via non-translatables.
|\<i\>\<b\>
|\<\/b\>\<\/i\>
|\<[biu]\>
|\<\/[biu]\>
|\<(br|hl|li|ul)\>
|\<\/(br|hl|li|ul)>
alwayslockyourbike
How would you handle Studio projects with lots of identical segments and many segments that contain unprotected HTML codes?