Re: changes in dbootstrap i18n (was Re: Hard newlines in dbootstrap messages)
>>>>> "ez" == Enrique Zanardi <ezanardi@ull.es> writes:
ez> OTOH, this weekend I will try to check in a few changes:
ez> - dbootstrap now uses a "gettext-alike" method for i18n. That
ez> means the sources are "gettextized" and the message catalogs are
ez> PO files that can be automatically updated/checked using simple
ez> "make" targets. I think that'll make our tasks as
ez> programmers/translators easier. OTOH, it may some Adam's macros
ez> for the documentation. Adam, I may build a trimmed-down
ez> "lang_<lang>.h" (or whatever.ent) at compile time if you still
ez> need it. Just tell me.
Hmm... Well, what I, really, are just the following (for all languages):
MSG-BASE-SYSTEM;
MSG-CANCEL;
MSG-CHOOSE-HOST;
MSG-CONFIGURE-BASE;
MSG-CONFIGURE-KEY;
MSG-CONFIGURE-MODULES;
MSG-CONFIGURE-NET;
MSG-CONFIGURE-PCMCIA;
MSG-DISK-BOOT;
MSG-DO-WITHOUT-SWAP;
MSG-DRIVERS-FLOPPY;
MSG-FLOPPY-BOOT;
MSG-INITIALIZE-LINUX;
MSG-INITIALIZE-SWAP;
MSG-INSTALL-BASE;
MSG-INSTALL-OS;
MSG-MOUNT-LINUX;
MSG-NEXT;
MSG-NO;
MSG-PARTITION-DISK;
MSG-REBOOT;
MSG-SELECT-ACTIVATE-SWAP-L;
MSG-SELECT-DISPLAY;
MSG-TITLE-MENU;
MSG-TZ-DIR;
MSG-TZ;
MSG-WAIT-STATE;
MSG-YES;
My scripts should be able to take any CPP defines and turn them into
SGML entities -- you can break it up into lots of files if you need to
and I can adapt pretty easily.
ez> I may check those changes directly in the main trunk, or create a
ez> branch if you see the need. Any suggestions?
If you are going to start hacking it up for the potato boot-floppies,
we oughta branch for the slink version. It makes more sense to branch
the maintenance line of code rather than the "under active development
code".
If you like I can take care of it and just branch now, or at least
make a tag so we can branch off that.
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: