On 08/09/2007, at 4:19 PM, Christian Perrier wrote:
I just validated the addition of the "win32-loader" package to "level 2" of Debian Installer related localized material. This package features an application that allows preparing and loading D-I from a system running MS-Windows. This makes the installation process for existing Windows users much more easier (see http://www.goodbye-microsoft.com).
I am willing to put time in to help Windows users. My optometrist visited me recently, and we had to wait for his laptop to load. And it wasn't even Vista (if it were, he might as well have come back the next day). I hope we can rescue some more people from that messy code.
This utility is maintained by the D-I team, mostly Robert Millan. I decided to include it in Debian Installer "level 2" because it is not strictly speaking a part of D-I itself, but, being included on Debian CDs, it is an important component of the Debian installation material. A few "translations" in this file are indeed settings of Microsoft Windows in your language. In case of doubt or if you're missing information and/or knowledge about Windows in your language, please contact the D-I team on debian-boot@lists.debian.org. The D-I i18n documentation (http://d-i.alioth.debian.org/doc/i18n/) has been updated to explain how to access the l10n material, particularly http://d-i.alioth.debian.org/doc/i18n/ch01s04.html. Please check that documentation before asking how to work on the package..:-)
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?
I find it difficult to remember for which packages I have write access, and for which I do not. Even when I write it down. Then I have difficulty remembering where I wrote it down. ;)
A couple of q.s about the PO file itself: ___ #: win32-loader.sh:36 #: win32-loader.c:39 #. translate: #. This must be a valid string recognised by Nsis. If your #. language is not yet supported by Nsis, please translate the #. missing Nsis part first. #. msgid "LANG_ENGLISH" msgstr "LANG_VIETNAMESE" ___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?
Thankyou for any help you can offer. :)from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
Attachment:
PGP.sig
Description: This is a digitally signed message part