написане Sun, 07 Feb 2016 19:34:59 +0200, Richard Ash <[email protected]>:
> On Tue, 02 Feb 2016 19:07:07 +0200 > "Yuri Chornoivan" <[email protected]> wrote: > >> написане Tue, 02 Feb 2016 16:59:03 +0200, scootergrisen >> <[email protected]>: >> >> > Den 01-02-2016 kl. 17:43 skrev Yuri Chornoivan: >> >> написане Mon, 01 Feb 2016 15:14:43 +0200, scootergrisen >> >> <[email protected]>: >> >> >> > I would prefer to not have the non-translatedable english text >> > during install then to have it there. >> > >> > Its silly to use alot of time translating the program and installer >> > and so on just for the user to be meet by english text right there >> > at the beginning. > > I could equally argue that it's silly to take information away from the > users just because it isn't currently translated - that text is there > because of the volume of (English-speaking) support requests which were > otherwise generated by the installer. So removing this page is not > practical to do. > >> Basically, what we need from developers is just a general consensus >> about the inclusion of such translation. >> >> If they have such consensus, you can translate the RTF file and I >> (or someone else) can prepare a patch to apply the translation. > The question is, how does this get maintained? I guess the same way as everything else. ;) > As far as I can see, we > will end up with one RTF file per language? Yes. // Windows way to translate things... > If there is a change to the > English RTF file (e.g. the recent website URL changes), then each of > those files has to be updated by the translators? The problem here is > managing that update, and what to do if translations are not actively > maintained. No problem. RTFs are plain text files, addresses are ASCII, so the perl magic can be used: perl -pi -e 's!foo!bar!' if /http! foobar.ext *.rtf Or just remove the translations as it was done with AppData. Translators will love developers even after such things. ;) > > Does anyone know if it works to have RTF files defined for some > languages, but not for all? It is done in Maxima InnoSetup file, so I guess it can be done for Audacity. Name: "de"; MessagesFile: "compiler:Languages\German.isl"; InfoBeforeFile: "audacity_InnoWizard_InfoBefore_de.rtf" Name: "uk"; MessagesFile: "compiler:Languages\Ukrainian.isl"; InfoBeforeFile: "audacity_InnoWizard_InfoBefore.rtf" > Does it show the English text for the > languages where no translation is available? Should be so according to specs. Thanks for your help. Best regards, Yuri ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Audacity-translation mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/audacity-translation
