Closed vv-monsalve closed 8 months ago
The stroke in lslash
needs to be more distinguishable, and avoid collisions.
Colombia
England SemiJoined
noted, will fix
@vv-monsalve , we tried a new approach to the design of /lslash, crossing the slash only on the left side of the loop. As I mentioned, none of these loopy models are meant to be used with bar/slash diacritics, but I feel this may be more recognizable now. If you and @davelab6 like it I can repeat in /hbar.
@josescaglione, inspecting the fonts at commit 3a4e55
this looks more recognizable indeed now. And similar strategy can be applied to all the bar or stroked letters.
The bar could be slightly below the connection stroke in models like the Englan SemiJoined at the Regular weight so it doesn't collide.
As I mentioned, none of these loopy models are meant to be used with bar/slash diacritics
Please keep in mind that these are our standard tests for all of our fonts, considering they always end up being used outside of the specific environments they were originally designed for.
hi @vv-monsalve I shifted the bar in h to the left as agreed. Regarding the 7lslash I reviewed the original Falski's design and decided to shift it up to avoid collisions. All of this will be visible in the next commit. Looking very nice I thin/.
I noticed that the bar in /hbar for the slanted designs look a bit shifted in your sample. Could you please send me the string you are using for that test? Want to double check it here
Hi @josescaglione this is the string used
ďá ďu gj ľk włw yły ółr fħ ílïlîl
Thank you, lets check again in the next commit but this should be ok now.
The fonts in the lang-build
branch at commit 658f99f
are looking much better now.
lslash
In some models, the
slash
looks like different positions for the stroke, in some cases showing some congestion with thel
loop.(Edit: moving here this issue previously reported in diacritics marks issue)