| From Thomas De Rocker <[email protected]> | Fri, 31 Aug 2012 23:51:00 +0200 | Subject: [Audacity-translation] REQUEST for translation strings of Audacity web site (and program) > > Can you provide examples of pages that are in active use where the > > strings are long? I don't think there are now many. > > The latest .po i submitted had a few changes in strings that contain > "faq_i18n". > Among them, there are "big" strings.
Sure, but as I pointed out, the audacity.SF.net FAQ's are unlikely to be modified further, so there is no point putting in a lot of work splitting up strings on that page. > > HTML code in the string can be replaced with %s by using printf's, > > but would that actually ease your complaint? Consider this as > > a sentence: > > > > Follow <a > > > > href="http://audacityteam.org/wiki/index.php?title=Lame_Installation#GNU.2FLinux.2FUnix_instructions";>these > > instructions</a> on our <a > > href="http://audacityteam.org/wiki/";>Wiki</a> to download and > > install a suitable LAME package from the internet. > > > > The sentence contains two URL's. There is no way to remove > > both the URL and any references to it without making four > > short, contextless strings. > > > > I don't mind having %s in translations, because it makes it easier (for me) > to have a better view (is "view" the right word?) of the translation. > Sentences should be left as a whole. OK. The others will have to say if they feel they need the URL in the string for context. I would guess not. > But like I said, if there is a "list" in > html, I would split every <li> entry into a separate string. <li> could be replaced with %s as well, but most current lists I can think of will probably be only a few lines long. Not everyone may agree with you about making a separate string for each <li>, for contextual reasons. So if they don't agree, they can say so :=). But such things would still probably only change when we change the list contents anyway. Splitting a long string up would make a new group of fuzzy strings that everyone would have to deal with. > > Unfortunately I doubt there are resources in Audacity Team to > > go through the site in one swoop and remove all cases of hardcoded > > URL's in strings. I am not translation manager (we don't have such), > > so I am definitely not going to do it, except piecemeal. If you (or > > anyone) wishes to provide a patch, please do so. > > I'm no programmer myself, so I hope someone else can help with that. > I'm not asking to do everything in one day... It can be done on-the-fly, > when you stumble upon a string that can be improved. Or as above, probably when it needs to be changed. > Just to make it clear, i didn't want to be rude by starting this > discussion. My goal was (and is) to improve and streamline the > translation process. No problem. 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
