On 2016-12-07, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Mittwoch, den 07.12.2016, 19:58 +0000 schrieb Guenter Milde:
>> I am not sure the Quote inset brings benefits for this feature.
> I doubt it is possible to implement it without the inset.
If quotes come in pairs, it can be implemented similar to brackets.
(Also for brackets there is a chance of mismatch due to other uses like
1) in enumerations
2) in smilies :-)
)
If quotes don't come in pairs (e.g. the Finnish quotes) it does not make
much sense to highlight matches.
>> +1 it may distinguish single left quote and apostrophe.
>> -1 it may still mix them, when the apostrophe is inserted with the
>> insert-quote LFUN.
> Which is _not_ an apostrophe (and thus the marking would actually be a
> feature).
However, at least in English, a typographical apostrophe and a typographical
single left quotation mark are considered the same *character* (not just
glyph):
The Unicode standard says:
0027 APOSTROPHE
* neutral (vertical) glyph with mixed usage
* 2019 is preferred for apostrophe
* preferred characters in English for paired quotation marks are
2018 & 2019
2018 LEFT SINGLE QUOTATION MARK
= single turned comma quotation mark
* this is the preferred character (as opposed to 201B)
2019 RIGHT SINGLE QUOTATION MARK
= single comma quotation mark
* this is the preferred character to use for apostrophe
Expectiong the user to inserting this character with different
keybindings depending on the use case is not user friendly.
The situation is different in German (or Czech, Slovak, Slovenian), where
the preferred "typographical" apostrophe character (2019 RIGHT SINGLE
QUOTATION MARK) differs from both single quotation marks ‚‘ (201A SINGLE
LOW-9 QUOTATION MARK, 2018 LEFT SINGLE QUOTATION MARK).
>> -1 strange results for documents with a mix of literal Unicode quotes
>> and
>> Quote insets
> It would only be supported for quote insets of course.
In case it is only implemented for the quote insets...
>> Mind, that some autors prefer use of literal Unicode quotes
>> (accessible
>> e.g.via AltGr+... over LyX's smartquotes keybinding.
> Then they don't get the feature.
... which IMO is an artificial limitation when OTOH supporting brackets.
>> Also quotes in imported text parts are not converted to insets
>> (and cannot be converted without guessing).
> But this can (should) be changed.
The guessing may be improved but will remain a guessing (see tex2lyx).
This is not a real problem, as long as back-conversion to the original
character is ensured and no other features depend on the correct guess.
Günter
