Re: [translate-pootle] Update files from templates - All strings marked fuzzy
Op Do, 2011-12-29 om 13:13 +0100 skryf Tim Anil: Hi Friedel, I use Translate Toolkit 1.9.0. I made additional tests with .pot file and update from templates: If the original string is 69 characters: 0123456789012345678901234567890123456789012345678901234567890123456789 And is changed to 70 characters: 01234567890123456789012345678901234567890123456789012345678901234567890 After update from template, then it's OK, the translation is marked fuzzy (98%) If the original string is 70 characters: 01234567890123456789012345678901234567890123456789012345678901234567890 And is changed to 71 characters: 012345678901234567890123456789012345678901234567890123456789012345678901 After update from template, then the translation is replaced with the .pot text defined in msgstr (which can be empty in the .pot file if msgid is the original string) and not marked fuzzy So it is as if very slight modifications of the original string (compared to its length) make loose the translation instead of marking it fuzzy. Could it be a problem of rounding (very close to 100 % ?). I don't where to look in the source code to check this. Ok, that helped. The issue is that the default parameters only considers strings up to 70 characters. You can check in translate/search/match.py for max_length=70, and change that to, say, 1000. If that fixes it, we can consider making that change in the translate toolkit for the next release. Regarding the problem with Mac OS X strings file, I searched bug database but didn't find a similar problem. I'm still not sure exactly what is up here. Is it related to the issue above (is it removed with the change I suggest)? If not, do you see any similar bugs with something like java .properties files? If not, feel free to add it to the bug database, and maybe have a look at what is happening if you can read a bit of code. Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/firefox-maybe-now-most-popular-africa -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Update files from templates - All strings marked fuzzy
Chris, thanks for your answer. I could identify what caused the TS translation to be marked fuzzy. If in the .ts original template file you have translation type=unfinished/translation instead of translation/translation, then for an unknown reason, the translated string will be marked fuzzy after the update even if the original string in the template is not modified. So removing the attribute 'type=unfinished' in the template file seemed to resolve the problem. But I made other tests with .pot file and Mac OS X properties file and had other problems: If I update from a .pot template with a slightly modified original string in the template, then the translation is lost (becomes empty) and not marked fuzzy although the original string is slightly modified. If I update from a Mac OS X properties template with an original string A modified to B in the template, then the translation is replaced with the new string B and the original string displayed before the translation is still the old one A instead of B. It's a real problem because it means that all translations with slightly modified original strings would be lost. I tried with the last version 2.2.0-alpha1a from trunk but the problems are the same. Does someone has a hint regarding these problems ? Thanks. 2011/12/21 Chris Leonard On Wed, Dec 21, 2011 at 5:00 AM, Tim Anil wrote: Is this the expected behavior ? It would mean that after an update, all strings should be reviewed again even if they were not modified. Is there a special setting to avoid this and that only strings with slight modifications are marked fuzzy ? We are running an older version of Pootle, but that is not the expected behavior. When I do an update from Templates, only mismatched strings are marked fuzzy. (e.g. typo correction in original or fuzzy matching to a new very similar string). I can't help you much beyond that, but I'm sure someone else can. cjl Sugar Labs Translation Team Coordinator http://translate.sugarlabs.org/ -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Update files from templates - All strings marked fuzzy
Op Wo, 2011-12-28 om 17:35 +0100 skryf Tim Anil: Chris, thanks for your answer. I could identify what caused the TS translation to be marked fuzzy. If in the .ts original template file you have translation type=unfinished/translation instead of translation/translation, then for an unknown reason, the translated string will be marked fuzzy after the update even if the original string in the template is not modified. So removing the attribute 'type=unfinished' in the template file seemed to resolve the problem. But I made other tests with .pot file and Mac OS X properties file and had other problems: If I update from a .pot template with a slightly modified original string in the template, then the translation is lost (becomes empty) and not marked fuzzy although the original string is slightly modified. If I update from a Mac OS X properties template with an original string A modified to B in the template, then the translation is replaced with the new string B and the original string displayed before the translation is still the old one A instead of B. It's a real problem because it means that all translations with slightly modified original strings would be lost. I tried with the last version 2.2.0-alpha1a from trunk but the problems are the same. Hallo What version of the Translate Toolkit do you use when you see this behaviour? Did you try exactly the same case with a PO file (translated entries becoming fuzzy with no change in the source text)? It might have something to do with the TS format, although I'm just guessing now. What you mention about the OSX properties might be unrelated. Can you search for that in Bugzilla to see if it is a known issue? Thanks Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/firefox-maybe-now-most-popular-africa -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Update files from templates - All strings marked fuzzy
On Wed, Dec 21, 2011 at 5:00 AM, Tim Anil tima...@gmail.com wrote: Is this the expected behavior ? It would mean that after an update, all strings should be reviewed again even if they were not modified. Is there a special setting to avoid this and that only strings with slight modifications are marked fuzzy ? We are running an older version of Pootle, but that is not the expected behavior. When I do an update from Templates, only mismatched strings are marked fuzzy. (e.g. typo correction in original or fuzzy matching to a new very similar string). I can't help you much beyond that, but I'm sure someone else can. cjl Sugar Labs Translation Team Coordinator http://translate.sugarlabs.org/ -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Update files from templates - All strings marked fuzzy
Does anyone how to hook ldap to pootle? I see it has this option, but I can't find any doc on this feature Thanks, Mason -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle