3 ms·
Making search work differently depending on the specified language just makes it unpredictable since not everything is marked up correctly.
by anoncake 6y ago
Making search work differently depending on the specified language just makes it unpredictable since not everything is marked up correctly.
- necovek 6y agoDo you have a better incentive in mind to mark text up properly? I'd even suggest browser to mess up formatting of non English letters (by using wildly different fonts) to encourage better semantic markup, but it is a bit hard-core and everyone would shout "compatibility breakage" at them :)
- zzo38computer 6y agoIf text is not marked up properly, then the user should be allowed to override that setting, but when it is marked up properly, such overriding should not be necessary. As long as it is user configurable which fonts to use for which language, I think that it does not break compatibility to do that. Actually, I think it is a bit good idea. The document should only specify the language and the style (e.g. bold, emphasis, normal, fix pitch, heading, etc) and then that combination is mapped to a font in the browser. (If the user has enabled use of CSS fonts, and such fonts are specified, then they would override those specified by the user. If the user has not enabled use of CSS fonts, then the user's fonts are always used.) This would be needed anyways due to the Han unification that Unicode does, anyways (and Unicode is very messy, anyways). (I mentioned before that Unicode can be good for searching, and if that is what you are doing with Unicode rather than for writing and displaying documents, then Han unification is probably desirable, although again the Duocode that I mentioned before may help even more.)