| From Thomas De Rocker <thomasderoc...@outlook.com> | Wed, 18 Sep 2013 20:32:14 +0200 | Subject: [Audacity-translation] Transifex - translation issue +updated Dutch translations > I updated the Dutch translations of Audacity on Transifex to the latest > versions. > > Website (with latest "addendum" string): > https://www.transifex.com/projects/p/audacity/resource/audacity-website/l/nl/download/for_use/
Thanks, committed and pushed. > Program (not edited this time): > https://www.transifex.com/projects/p/audacity/resource/audacity/l/nl/download/for_use/ So have you changed the string translations since http://code.google.com/p/audacity/source/detail?r=12562 - meaning that the "not edited" file should be committed? > I have one remark... I have already tried to solve this issue (mostly MY > issue): > the fact that each "string" in the translation files is not a string, > but almost a whole page of text... for us translators, it's a lot of > work to have to translate everything twice or more. It reduces the context for each sentence to be a string. It's also more coding for each bullet point in a list or each sentence to be a string. Separate lists would ideally be a separate string. Do I assume the problem comes if the long string changes? It then becomes "fuzzy" and it is hard to see what changed? You could perhaps look at the previously committed .po file to see what changed, or better, look at the diff that generated the changed string - in the case of the "addendum": http://code.google.com/p/audacity/source/detail?r=12565 . Click on the "+" on that page to see what changed. A way to find the diff more easily may be to identify the text in question in the website.pot file: http://audacity.sourceforge.net/locale/audacity_website.pot . This shows you the file that changed then you can go to that file's diff from: http://code.google.com/p/audacity/source/browse/#svn%2Fwebsite%2Ftrunk%2Fhtdocs . > Why was the addendum string added to an existing one?? Why wasn't > it made into a separate one, so it would be easier to translate? As I read it, the array is written to only accept a single string in the body. > And again... why do we even have to translate the urls? I thought > the goal was to remove the html code as much as possible and replace > them by tags? Over the last week i had to read and re-read strings > where the urls had one or two characters difference... really annoying. If the coder has time to put the real url's of new strings separately (outside the string) that's much preferable. If a string changes substantially, then that may be an opportunity to move the real URL outside the string. I don't think anyone has time to fix the existing strings that don't otherwise need to change - indeed it would break translations to do so. > So again, please: > - split up those chunks of text into small translatable sentences >(I prefer one sentence or list item per string)) I don't think that can be easily done in arrays. Other translators will probably complain that they need the context of the sentence or paragraph that precedes the list. > - replace the html code with tags, so the developers can change the > urls without bothering the translators... See above. Generally the site changes little except at release, and at release time the time pressure is considerable. This was particularly so for 2.0.4 release with Team members being on holiday. Those that remained had to do extra work on tasks they do not normally do. Gale ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Audacity-translation mailing list Audacity-translation@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/audacity-translation
