On Mon, 14 Oct 2002, Markus Kuhn wrote:
> Jungshik Shin wrote on 2002-10-14 06:37 UTC:
> > When I made a patch, I wrote to the maintainer of cdrtools,
> > but his response was not so positive. At first, he asked me whether
....
> Try again, he's just busy. (I interacted on this with him as well)
Ilya did (I sent him an email on his behalf becaus his ISP
is blacklisted). In his reply, he wrote that mkisofs is currently frozen
for an imminent major release. Perhaps, in next cycle of development,
iconv() will be considered. One of his concerns was how to detect the
availability of iconv(3) with autoconf. I pointed out that iconv.m4 for
autoconf had been written by Bruno. So, this should not be a problem.
However, I had to tell him that there's another hurdle to overcome.
My patch hard-coded 'UTF-16LE' as the codeset name for 'UTF-16 Little
Endian', but it's not very portable. There should be a way to detect
the codeset name to use with iconv(3) on a given platform for UTF-16LE.
Is there any autoconf macro written for this?
One way I can think of is to first detect the codeset name for UTF-8
(utf-8, utf8,utf_8 and uppercase variants) by iconv_open with two
identical codesets and then try iconv_open with a set of candidate
names for UTF-16LE and the detected UTF-8 name. Then, invoke iconv()
with a known UTF-8 string and check the result for endianness.
An alternative is to just make it user-configurable at run-time.
This is easier for programmers, but not so user-friendly...
> He means ISO 13346 and its profile UDF 2.01.
<info. on 13346/UDF. snipped>
Thank you for the info. on ISO 13346 and UDF.
Jungshik
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
