Date: Tue, 29 Jul 2014 23:40:14 -0400 From: "Garance A Drosehn" <drosih@rpi.edu> To: freebsd-arch@freebsd.org Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Message-ID: <1092D020-F782-4587-A199-C7313BC2CD20@rpi.edu> In-Reply-To: <448BB170-6DDC-442B-A5C5-973EC35FF7B9@rpi.edu> References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <CAETOPp13H7kyLy-1VJRDOsDbOh8A1MWZDxw1xHUBsxTRtMfc7g@mail.gmail.com> <20140728054217.AC1A0580A2@chaos.jnpr.net> <20140728055336.GJ50802@ivaldir.etoilebsd.net> <CAETOPp3hJB8Gj%2BPMj3N951krnNqCYiAOY-cPHxMCBy1CQXWJaQ@mail.gmail.com> <A1E63A7A-BB38-4CC3-B5EC-B251BE990572@mail.turbofuzz.com> <20140729230345.31E9B580A2@chaos.jnpr.net> <53D85495.4050408@mu.org> <448BB170-6DDC-442B-A5C5-973EC35FF7B9@rpi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29 Jul 2014, at 23:19, Garance A Drosehn wrote:
>
> In any case, I am interested to see how the GSOC project works out, or
> whatever happens with this libxo project.
I also wanted to highlight an issue that Simon brought up in the initial
message for this thread:
"The main open issue (assuming this functionality is still desired)
is support of wide characters.
We figure the worst case solution is a sed(1) script to generate
the wide version of the API from the normal one, but perhaps simply
always using UTF8 would be a better solution?"
In my own experiments I've pretended that all the output 'lpq' generates
is simple ascii, although that's not necessarily true. The filename
field is set by whatever generated the output, which might be a PC or Mac
which may or may not be unicode-aware. The field might be gibberish (aka
"invalid unicode"). Obviously "pretending" is the wrong way to handle
this issue.
--
Garance Alistair Drosehn = drosih@rpi.edu
Senior Systems Programmer or gad@FreeBSD.org
Rensselaer Polytechnic Institute; Troy, NY; USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1092D020-F782-4587-A199-C7313BC2CD20>