Op Wo, 2010-04-07 om 14:10 +0800 skryf Bernard Chan: > Hi everybody, > > We have a PHP-based project with POs managed by Pootle. We found that > when the original message contains \n, Pootle tends to remove the \n in > the copied message in the translation entry when I click the "Copy" > button while editing a translation. Is this behaviour intended, as the > newline omission is causing some messages being messed up on the screen > as our translators (me included) are not aware of this? > > I looked at the POs and those messages contain "#, php-format". > > We're on Pootle 2.0.3. Thanks in advance for any input.
I think I have seen this, but I don't think we had a bug report about this, so it might have evaded the attention of developers. I don't think this is related to being php-format. The solution I want to propose, is for Pootle to keep the suggested value (escaped as Pootle expects it) hidden in the form, with changed punctuation, so that users will actually get their own punctuation instead of that used by the English. Virtaal already does that, and I think it can be a small time saver for some people. This way it would copy No file named "%s". to No file name « %s » in French, the non-breaking spaces as needed by French besides its quotation marks. Virtaal already does some of this. This could be a nice task for someone who wants to help a bit with Pootle development. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/provisionaly-done-localisation-guide-amharic ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
