![]() ![]() in Translations queue, choose the files for translation and xliff version, 3.4.9).Īn impossible to translate 3-segment xliff. The same goes for xliffs 1.1 and 1.0 generated via WordPress.Īn orderly, well-segmented xliff file that is easy to manage in CAT tools such as Trados and Wordfast 3 Pro (v. Do you think this awkward segmentation has anything to do with the indeed? If yes, what's causing it to appear and is there any way to solve this problem? If not, what could be the cause for this awkward segmentation? Otherwise generating xliffs via WordPress doesn't make sense, as that kind of segmentation defeats the purpose of CAT translation. However, the tag is visible ONLY in TextMate (for MacOS) when I use TextEdit, the tag is not visible, neither is it visible in the WordPress editor. I think it may have something to do with the tag that appears throughout the xliff (see screenshots: ss3, ss4). 80% of the 900-word document (see screenshots: ss1 and ss2, made while using Trados). Both CATs divide the xliffs into 3 segments, the middle segment consisting in c.a. Have WordPress-generated xliff files (1.2) translated in Trados and Wordfast Pro 3 (v. The CATs in question are: Trados Studio 2015 and Wordfast Pro 3. ![]() There are a couple of issues I'd like to present, I'll try to be as specific as possible. Last updated by Joanna 4 years, 5 months ago. This topic contains 6 replies, has 2 voices. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |