> Thu, 30 Aug 2012 12:44:45 +0300 Thomas De Rocker > <[email protected]>: > > I have a request. I'm sure it's already mentioned before by other > translators, but I'd like to ask it again. Is it possible for the > people managing the site to make all monstrous big strings into lots > of small ones? At the moment, it's a hell for translators to have to > search for a modified URL or word in a "string" that takes up a whole > page!
There is never any translator consensus about how long a string "should" be. As pointed out in the replies, short strings can leave you with no context to work with. In the last update, I rewrote some strings which were only two or three words as a sentence or two. Which pages exactly do you think are the worst offenders for strings being too long? > I know the source strings (.pot) is online. What I meant is in > case of changing the complete .pot, that we should have a backup > location for the "old" .pot and .po files so translators can still > get the old translations to copy them into the new files. The .po files are in SVN so you can always find previous ones for your own locale: http://code.google.com/p/audacity/source/browse/website/trunk/htdocs/locale . The .pot files are not in SVN but you can always keep a copy of each one yourself before downloading the new one. It isn't currently possible to make decent comparisons between .pot's, however. Gale ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Audacity-translation mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/audacity-translation
