Hi,
[I am copying this to the folks on [EMAIL PROTECTED]
folks, neither will nor I are on the mailing list, and I would
appreciate relevant responses to be CC'd to us]
>>"Will" == W L Estes <[EMAIL PROTECTED]> writes:
Will> I'm beginning a beta release process for flex. If
Will> you'd like to take a look at the new code to see what it does,
Will> then go ahead. It can be found in:
I am still in the process of evaluating the differences, but a
quick preliminary scan shows that flex includes unistd.h
unilaterally. Unfortunately, this makes it fail on MS platforms --
wrapping the inclusion in # ifndef _WIN32 .. #endif would extend flex
scanners to another (popular) platform at a low cost.
Will> From our previous discussion, I know that the debian flex
Will> package includes a set of changes to allow flex to work with
Will> gettext.
Will> I'm not familiar with gettext but I would like the flex distribution
Will> to have i18n support and any pointers you can offer in this regard
Will> would be greatly appreciated.
I'll have to call in some other folks who did the heavy
lifting for the internationalization effort. As far as I can see,
we'll need to update the .po files, but most of the changes that
Debian made to flex should still apply cleanly.
Folks, the .po support for flex 2.5.4a is in debians flex
source package; and the new beta is in
ftp://ftp.uncg.edu/people/wlestes/
How much work would it take to update the .po files?
manoj
--
Buck-passing usually turns out to be a boomerang.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
