>> Do you mean in the input or in the output? Right now, `...' in the
>> input has two purposes.
>>
>> (1) It is used as a poor-man's substitute for inline code snippets
>> – the thing Nikhil is talking.
>>
>> (2) It is *really* used for quotations, i.e., `foo' should be
>> converted to ‘foo’. Note that I prefer ‘foo’ over “foo”, since
>> it is less intrusive to my eyes.
>>
>> This should be disentangled. However, I don't want to throw away
>> (2) completely.
>
> Should I look at only changing inline code blocks, or all quotes (in
> input), then?
Well, `...' should be eventually resolved into `...` and '...'.
> Also, in the output, should we retain ‘ and ’ (‘... ’)
> or should I change those to just single quotes ('..')?
I prefer `lsquo' and `rsquo'.
>> While the majority of `...' is case (1), we have a lot of (2) also.
>> In other words, a fully automated conversion is not possible IMHO.
>
> It seems like there are 981 instances of quoted text in the docs. I
> will try to come up with a method to automate this, if possible.
>
> We can always do a manual cleanup later.
OK.
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
