![]() ![]() Pseudo-translation populates translations with a quasi-random jumble of characters, optionally also more characters than you had in the source. MemoQ has a function that allows you to detect such problems up front, as soon as you are done setting up the file format filters to deal with the input. Will the text fit on the screen? Will all the special characters display correctly? If you’re working from English into, say, German or Hungarian, they tend to be a We used memoQ’s Regex Text filter to extract exactly the text that needs to be translated, and we threw the regex tagger at the result to eliminate all the nasty inline codes that still remained.īut, but, that nagging feeling… What if I did mess up something with all this regex magic? It would be horrible if I spent hours translating, only to find out at the very end that half the text is missing, or that there was an odd little difference in the output that means the developer cannot reinsert the files into the app.Īlso, translations have a nasty habit of being longer than the original. If you read the last two installments, you’ll agree that we’ve made a lot of progress to get Inkpad’s strings translated. ![]() UPDATE: Turns out Michał Tosza beat me to this one he has a super concise and clear video about pseudo-translation Localizing an iOS drawing app with memoQ, one cliffhanger at a time. ![]() Did I screw up the file filter? Testing the iOS localization package with pseudo-translation :: Jealous Markup $jm> _ Plots Builds Texts Did I screw up the file filter? Testing the iOS localization package with pseudo-translation ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |