| From Thomas De Rocker <[email protected]> | Fri, 31 Aug 2012 13:39:11 +0200 | Subject: [Audacity-translation] REQUEST for translation strings of Audacity web site (and program) >[...] I agree that a string shouldn't be a few loose words, but a complete >sentence with a meaning. > > However, the strings I'm talking about are the ones which become longer than > 2 or 3 sentences... here is an example: > > <p>Because of software patents, we cannot distribute MP3 encoding > software ourselves. Follow these instructions to use the free LAME > encoder to export MP3 files with Audacity. > <h3 id="win">Windows</h3> > <ol> > <li>Go to the <a href="http://lame1.buanzo.com.ar/";>LAME > download page</a>.</li> > <li>Under "For Audacity on Windows", left-click the link > <b>"Lame v3.99.3 for Windows.exe"</b> and save the file > anywhere on your computer. <b>Do not right-click the link to the > .exe file.</b> </li> > <li>Double-click <b>"Lame v3.99.3 for > Windows.exe"</b> to launch it (you can safely ignore any warnings > that the "publisher could not be verified").</li> > <li>Follow the "Setup" instructions to install LAME for > Audacity. Do not change the offered destination location of "C:\Program > Files\Lame for Audacity".</li> > <li>The first time you use the "Export as MP3" command, Audacity > will ask for the location of <b>"lame_enc.dll"</b>. > Navigate to "C:\Program Files\Lame for Audacity", select "lame_enc.dll", > then click "Open" and "OK".</li> > <li>If you prefer the Zip option for the LAME download, save the > zip file to anywhere on your computer, extract "lame_enc.dll" to any > location, then show Audacity where to find it as in Step 5 > above.</li> > <li>In case of difficulty, please view our <a > href="http://audacityteam.org/wiki/index.php?title=Lame_Installation#Windows_Instructions";>more > detailed instructions</a> on the <a > href="http://audacityteam.org/wiki/";>Audacity > Wiki</a>.</li> > </ol> > <h3 id="mac">Mac OS 9 or X</h3> > <ol> > <li>Go to the <a href="http://lame1.buanzo.com.ar/";>LAME > download page</a>.</li> > <li>Click to download either <b>"Lame Library v3.98.2 for > Audacity on OSX.dmg"</b> or > <b>"LameLib-Carbon.sit"</b>, according to your operating > system.</li> > <li>Double-click the .dmg to extract "Lame Library v3.98.2 for > Audacity on OSX.pkg" to Finder, or use Stuffit to extract "LameLib" from > the .sit (either of these may happen automatically).</li> > <li>Double-click the .pkg to install > <b>"libmp3lame.dylib"</b> in /usr/local/lib/audacity, or > save <b>"LameLib"</b> anywhere on your computer.</li> > <li>The first time you use the "Export as MP3" command, Audacity > will ask for the location of "libmp3lame.dylib" or "LameLib". Navigate > to that location, then open the file and click "OK".</li> > <li>In case of difficulty, please view our <a > href="http://audacityteam.org/wiki/index.php?title=Lame_Installation#Mac_Instructions";>more > detailed instructions</a> on the <a > href="http://audacityteam.org/wiki/index.php";>Audacity > Wiki</a>.</li> > </ol> > <h3 id="nix">Linux/Unix</h3> > 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.
In this instance, the strings won't be changed because the FAQ's on audacity.SF.net are being wound down in favour of FAQ's in the Manual (if we can find people to translate the Manual). So the FAQ's above are unlikely to be changed further. Another example of long strings I can think of is the old features-1-3-a page, but again, that won't be modified further. Can you provide examples of pages that are in active use where the strings are long? I don't think there are now many. > This should be split in (meaningful) smaller sentences, with as little > code as possible. In my opnion, translators shouldn't have to deal with > html codes. All <li> codes can be left out of the translation if every > entry of the <li> would be translated separately. 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. > And also, a previous point I made: if the above string is edited and > becomes fuzzy, a whole page is shown in English on the web site, > which makes it difficult for people who don't understand English as > good as we do... I think people who have recently worked on the site understand that, whereas it was not understood in the past. > And one last point: I noticed that most string changes are urls. If the > source strings are made so that urls don't have to be translated, these > urls don't have to be edited for over forty times (once for every > language). Like I said, translators shouldn't have to deal with code... As above, that can be done with printf's, and if I come across an example that lacks them, I now tend to add them, so that the actual URL is not in the string. This makes sense for the reason you state. But you will still have %s or similar in the string. 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. Thanks, 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
