On Tue, Jun 27, 2000 at 11:49:34PM +0900, Hiroki Sato wrote:
> Nik Clayton <[EMAIL PROTECTED]> wrote
> > [ That schema is not set in stone, and certainly requires more work.  In
> >   particular, we probably need "lang" and "encoding" options on the
> >   <comment> element, to support comments in more than one language. ]
> > 
> > LINT would then become a skeletal file for things which don't fit this
> > sort of pattern, and the full LINT would be generated by a script which
> > parsed the above and the skeletal file to generate the full LINT.
>  I think it is difficult to maintain the files because few editors
>  can handle various languages/encodings at the same time.
>  So, especially for translators, it is better that the .xml files
>  are separated on a encoding/language basis.

Possibly.  I was thinking that the only thing that would be language
specific about each driver would be the comment section.


All the other stuff is language independent.

That being the case, it wouldn't be too hard to do

    <commant lang="ja_JP.EUCjp">...</comment>

    <comment lang="es_ES.ISO_8859-1">...</comment>

and so on, would it?

Or does loading Japanese text in to a non-Japanese aware editor scramble
the text?
Internet connection, $19.95 a month.  Computer, $799.95.  Modem, $149.95.
Telephone line, $24.95 a month.  Software, free.  USENET transmission,
hundreds if not thousands of dollars.  Thinking before posting, priceless.
Somethings in life you can't buy.  For everything else, there's MasterCard.
  -- Graham Reed, in the Scary Devil Monastery

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to