-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect letter spacing in both tangram-es and js for many shaped languages #94
Comments
I thought we had addressed this in another style but looks like all styles have this issue. refill-style/refill-style.yaml Lines 108 to 109 in bd579c7
Won't work for many other languages (not just indic). |
I can't read Hindi but even I can tell that ain't right 😂 The The |
That sounds reasonable (with respect to disabling for blocklist of shaped languages) to me @matteblair. Thanks |
Oh I just realized - adding spaces between letters makes it such that |
Can we apply non breaking space?
…On Tue, Jul 7, 2020 at 11:53 Matt Blair ***@***.***> wrote:
Oh I just realized - adding spaces between letters makes it such that
text_wrap won't work as expected because it will be applied on the output
string. The spaces make it such that a line break can go anywhere in the
word. So unless the "expansion" can be done properly in the font rendering,
text_wrap won't be usable here :\
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#94 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGQIO4UUSXSOVUEJGNGHE3R2NVKBANCNFSM4ORANGWA>
.
|
Looks like maybe font-stretch is what "text expansion" is called in CSS. Does this property work with Canvas font rendering? |
CSS letter spacing would add space between the characters.
|
Look at the name for North America (उत्तरी अमेरिका). I think I have mentioned about this issue in some other mapzen base style and the underlying problem was how " " was being used, or on those lines. Will try to dig the issue if I can, or else @nvkelso might remember this too (quite confident I discussed this and solved it with him).
The text was updated successfully, but these errors were encountered: