On Wed, Oct 26, 2022 at 03:12:17AM +0200, Vincent Lefevre wrote: > > It seems like the opposite would be the case that people will be unable > > to find the minus sign when searching the document because they are > > unable to type it in on their keyboards. > > Well, that's a potential issue with all non-ASCII characters. This > is not specific to the true minus sign. The solution is to make the > Info reader handle such cases:
For that issue, in the release to come, there is a new customization variable for texi2any, ASCII_PUNCTUATION, that uses ASCII only for punctuation and similar (I haven't checked what it does for @minus, but I guess it falls in that category). > * Make an ASCII character also match similar non-ASCII ones. This > solution is implemented in Firefox, for instance (and it can be > disabled to get exact matches). > * Alternatively, transcode everything to ASCII. This can already > be done by running info with LC_CTYPE=C. I do not think that it is a good idea to go further in that direction, to me this should stay a trick to get something viewable, not a way to obtain a specifc output. -- Pat
