5/5/2023 0 Comments Trados xliff editor![]() ![]() ![]() So segmentation is usually by trans-unit. An additional problem we have is that XLIFF is a bilingual file and if the content is partially or fully translated then segmenting the content outside of the trans-unit has at least one complication and that is how does the computer know where to segment without understanding the language? Sometimes it might be fairly straightforward, but other times it is not. When localizing of course you need to be able to interpret the markup so it can be protected, and this is very tricky. The cynical side of me would say this is because it's easier to just dump the content into a CDATA section than it is to properly consider how it should be handled for localization. Therefore, let me cry for help again: is everyone here absolutely sure nothing can be done to carry out WordPress / WPML projects with Studio 2017 (in terms of fixing the very-large-segment issue)?Īlways an emotive topic this one because on one hand it's very poor practice to put markup inside CDATA sections for XLIFF files as they are intended to be interpreted as plain text, and on the other many providers of XLIFF do exactly this. And what I'm observing is a situation that is. Put bluntly, the idea behind Studio must be to perform translation projects that real-world clients wish to pay for. It is perhaps the tragedy of my situation that I can't afford to appreciate the wonderful technicalities and the different flavours of this or other tag inside some computer file. While a competitive CAT tool seems to be able to simply crack on with it on default settings. Therefore, I'm a bit stuck here: it is confusing to me how my CAT platform of choice seems to be unable to support a straightforward website translation project (if you quote my clients) which was taken from world's most popular website management system (that's undisputed). On the other hand, I very much wish to stay entirely loyal to the SDL Studio / GroupShare suite, as a business principle. They just want their website professionally localised into their desired languages, preferably very quickly, and you really can't blame them. I only own an LSP that tries to serve some very decent clients, none of whom wish to entertain the various detailed IT problems. However, if you imagine yourself in my situation, I don't own WPML. Indeed, I do observe exactly what you're describing: a single large translation unit which you can't do anything with. I very much appreciate your contribution. Please would anyone be able to advise the quickest way to correct that segmentation issue? ![]() Surely, there must be some setting deep inside the newest Studio that I'm not noticing? To be honest I'd rather need a real-life fix which simply works, just like the other CAT does it. I admit I noticed some relevant information on this Forum regarding legacy Studio 2014 but that piece of advice is thankfully very now old - because it seemed to be a multi-stage workaround of incredible technical complexity. But then I've put the same xliff into one of popular alternative CATs and hey - what was 3 segments in Studio 2017 (one big blob plus 2 one-liners at the bottom) turned out to be 94 proper segments in the other CAT! I suppose this makes WordPress / WPML innocent enough. I don't want to make any unfair comparisons but in the interest of research the following might also be useful to pre-empt: I initially thought the segmentation error could be a WPML issue. The consequences of this are not nice: you can't use MT, you can't use your TMs, you can't even translate anything manually either, for fear of damaging the file so it won't fit back into the website. The whole file becomes just a few segments, with lots of line spaces in between whole blocks of text. There seems to be a consistent issue with such xliffs in Studio in that the translation projects are not being broken down into segments properly. I was wondering whether someone could help with a recent issue we're having.Įssentially, we get website translation projects in the form of xliff files, generated from WordPress with WPML. ![]()
0 Comments
Leave a Reply. |