On Mon, Jan 23, 2012 at 05:20:42PM -0800, Karl Berry wrote:
> In HTML, those quotes are “ and ” in
> the default case. Is it ok?
>
> Not [lr]squo? Always been traditional to use single quotes for @file
> etc.
Sorry, of course it is [lr]squo.
> So, should I proceed with ` becoming ' in ascii in info/Plaintext
> output?
>
> I fear so. I can't see any convincing reason for us to refuse.
Ok.
> I agree. Inside @code/@example is different.
> And that output is already controllable with @codequote*, so fine.
But only for TeX. Right now @codequote* information is not used in
any output format in tp, if I remember well.
> and U+2018. That would seem rather logical to also transform ' and
> ` to unicode U+2019 and U+2018 in that case too.
>
> I agree.
Ok.
> The XML output should do those transformations too?
There are special entities used (when not in @code/@example):
$result =~ s/``/&textldquo;/g;
$result =~ s/\'\'/&textrdquo;/g;
$result =~ s/---/&textmdash;/g;
$result =~ s/--/&textndash;/g;
it would be consistent to add &textrsquo; and the transformation to the right
unicode in the dtd, sure.
In docbook, everything is already converted to unicode code points.
--
Pat
