On Mon, Jan 23, 2012 at 02:25:54PM -0800, Karl Berry wrote: > Paul -- I dislike copying two big lists, so I'm just going to reply > here. > > I am of course fully aware of the coding standards change. > I agree that @file and the like might as well generate '...' now in > Info/plaintext output, given the mandated change. Patrice, wdyt?
Can do that easily. In HTML, those quotes are “ and ” in the default case. Is it ok? They are customized using OPEN_QUOTE_SYMBOL / CLOSE_QUOTE_SYMBOL. In plaintext/Info output, they become U+2018 and U+2019 if enable-encoding is set and @documentlanguage utf-8 is set too (as discussed recently). > To go all the way, makeinfo would have to change an input ASCII ` to an > output ASCII ', when just regular text is `quoted'. That just seems so > bizarre to me. I cannot argue that there is any other way to be > "compliant", though. Sigh. Can do too, even though I don't really like that. Although, I agree that this is unavoidable if one want to have unicode quotes different from ascii quotes. So, should I proceed with ` becoming ' in ascii in info/Plaintext output? Currently, in html, ' is changed to ’ and ` to ‘ except if in @code/@example. I think that it should be kept that way. There is no equivalent of OPEN_QUOTE_SYMBOL / CLOSE_QUOTE_SYMBOL in this context, I am not sure that it should be added. I think that in other output too, no change should be done in @code/@example. For now, ' and ` are not transformed to unicode points, like --- -- `` '' are in text/plaintext/info if enable-encoding is set and @documentlanguage utf-8 is set too. They are in DocBook, to U+2019 and U+2018. That would seem rather logical to also transform ' and ` to unicode U+2019 and U+2018 in that case too. Ok? -- Pat
