Re: changes in dbootstrap i18n (was Re: Hard newlines in dbootstrap messages)
On Fri, Mar 19, 1999 at 10:52:18PM -0500, Adam Di Carlo wrote:
> >>>>> "ez" == Enrique Zanardi <email@example.com> 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):
Of course everybody else on the list already knows the verb you and me
have carefully omitted from the previous sentences is "have to
> 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.
Uh, well, as there are no CPP defines in my current sources (gettext is
nice, defines are ugly) :-) I may build the .ent file just as easily from
the PO files. I'll have a look at it today (sunday).
> 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
> 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.
Most of the changes that have been commited to the repository last week
are for the potato boot-floppies (at least the powerpc stuff is). But
I've seen you've already tagged the current version (thanks!), so I guess
that means I can upload my changes to the main trunk.
Enrique Zanardi firstname.lastname@example.org