Robert, questions for you at the end of this mail. > OK, I've read the doc., and I've grabbed the POT file from HTTP. I've been > trying to check the package out via SVN, using my Alioth username, but the > connection keeps timing out. Does that mean (in an indirect way) that I > don't have write access, and should use anonymous access? You definitely have write access as you have write access to the whole D-I repository. If the conneciton is timing out, this is probably something else. > Is this correct? I don't know if NSIS supports Vietnamese, since I don't > use Windows, and wouldn't if I were paid to. (I mean, unless it were a > really, really large amout of money... Then I would take the money and use > it to install a decent operating system on lots of computers!) > > I know NSIS messes up our OpenOffice.org installation in some peculiar way: > apparently NSIS doesn't support UTF-8 yet. Talk about "behind the times"... > that is ARCHAIC. > ___ > > #: win32-loader.sh:52 > #. translate: > #. This must be the string used by Windows to represent your > #. language's charset. If you don't know, check [wine]/tools/wmc/lang.c, > #. or http://www.microsoft.com/globaldev/reference/WinCP.mspx > #. > #. IMPORTANT: In the rest of this file, only the subset of UTF-8 that can > be > #. converted to this charset should be used. > msgid "windows-1252" > msgstr "" > > #: win32-loader.sh:57 > #. translate: > #. Charset used by NTLDR in your localised version of Windows XP. If you > #. don't know, maybe http://en.wikipedia.org/wiki/Code_page helps. > msgid "cp437" > msgstr "" > ___ > > Both these references provide only "1258" for Vietnamese. Normally, our > language requires UTF-8. 1258 would be a legacy encoding, pre-UTF-8. I > would rather avoid if it possible, but if this is NSIS, we can't, since it > doesn't support UTF-8. <sigh> > > So, do I input "windows-1258" for the first string, and "cp1258" for the > second? Let's ask Robert Millan.
Attachment:
signature.asc
Description: Digital signature