Philipp Stephani

This is a duplicate of https://github.com/khaledhosny/luaotfload/issues/37 (the issue was already fixed last year). However, there is something fishy since the fixed file wasn't included in the last release.

Just for clarification: The fix to the blacklist has already been committed a year ago, but the latest release (which is dated May 2012) didn't include that file for some...

As I said, that has already been fixed upstream, but somebody has to release a version that contains the fix.

Handling such filesystems is generally hard or impossible on a library level. For example, there's no way to figure out whether `/path/to` and `/path/TO` will refer to the same directory...

That might well be one of the errors in the STIX table that Hans recently mentioned. U+29F5 is called the reverse solidus operator in Unicode. Many fonts (but not Cambria...

I don't think we should introduce an option for this (and, by extension, for every questionable characters). Probably we should implement ConTeXt-like "typescripts" or at least individual packages for specific...

@khaledhosny please have a look at this. (But ultimately it has to be fixed at the STIX side) I agree that font bugs should be fixed upstream, but it can...

It is not a bug, just a design issue: - Unicode unmistakably states that U+2216 is the character that denotes set difference - U+29F5 is the reverse solidus operator -...

I don't think there is anything similar in Unicode, so `\mapstochar` itself probably has to stay buggy (or we may choose to undefine it). `\xmapsto` should be redefined using the...

``` However the code you provided makes the whole xmapsto arrow is invisible ``` Uh, that shouldn't happen, of course. Once again I forgot that we switched from family 4...