Missing Points at Extrema (2 in NotoSans, nearly all errors in Amiri)įor some errors, FontForge offers an auto-fix, but not for all and it might have some side-effects, so I did not use it.Flipped References (5 in NotoSans, none in Amiri I guess).Wrong direction (Amiri, very few errors).Self Intersecting (Amiri, very few errors).There are 5 different types, 4 types are in the fonts before merging
I suppose this is OK for this purpose - if not, please tell me (the link is nowhere else thanks for this regarding the errors above:
#Arial arabic font free#
It is using the free CDN for OpenMapTiles. Here is a map for demonstration purpose using the merged Noto/Amiri font locally hosted. I didn't investigate further, because the text labels are looking fine for me (the Latin ones and "Khémisset"). Maybe it is only a violation of a standard or something else and the fonts are working fine with these "errors". Validation of the two fonts before merging them (the fonts are only opened in FontForge) gives already errors, 7 for Noto Sans and a lot of them for Amiri:įor me it looks like the "errors" are in the fonts "by default" and are not a result of merging them.Īlso I am not sure if these are really errors or if they are serious, because even Noto Sans has "errors" by default. There is also a warning when opening Amiri in FontForge: Note the scrollbar, there is much more in the list available in Regular / Regular Italic / Bold / Bold errors are not really on merging I think, there is an option "Validate Before Saving" which gives:Ĭlicking on "Review" gives this (it is still named Noto Sans because I merged Amiri in Noto Sans):.according to "VERY attractive to those working with Arabic".seems to be already a "merged" font with Latin/Arabic characters included.What about doing some tests for using "Amiri" instead of "KlokanTech Noto Sans Regular / Bold / Italic"? Which fonts are merged in "KlokanTech Noto Sans Regular", one font with Latin and one with Arabic characters? If yes, I would think is right that something went wrong merging the fonts or the RTL-Plugin is not compatible with fonts merged this way. It looks like there is nothing is this the font used for "KlokanTech Noto Sans Regular" (I did not find a ""Noto Naskh Arabic Sans Regular") ? This is how it looks like with NotoNaskhArabic-Regular.ttf from turned into PBFs and locally hosted. It must be clear what is wrong even to people who can't read thanks for checking! I am only able to visually compare:-) Please, when reporting details regarding this problem always provide a single label image as a visual clue - so we have real examples - like for the "Khemisset" above. but I may be wrong - if Mapbox hosting normalise/adjust the Unicode text representation inside of the uploaded vector tiles automatically. This led me to a conclusion that the problem is in the font. When I switched to KlokanTech Noto font on Mapbox platform the labels looked broken.
I have tested our tiles by uploading them to the Mapbox hosting, and using them with the Noto Naskh Arabic and Arial Unicode MS fonts on Mapbox platform - and the labels looked correct.
I see text which looks correct to me in Arabic: The GeoJSON form of the vector tile with test "Khemisset" town above is at: Maybe Unicode NFC or some Arabic specific simplified Unicode encoding is required? Maybe the Unicode text in our vector tiles must be normalised or preprocessed - to have a font-system compatible representation of the initial/final characters in the Arabic words. We have no customer willing to support the work on fixing this, so this ticket has a lower priority than other tasks (so your "while this is being fixed" is not true - nobody works on this actively).Īnyway, if you have some time - please dig deeper into this.