> I'll open up a ticket and upload a patch as soon as it's finished
> (it already works, but I want a proper solution).
Great, thanks!
> *By the way:* how about TABs? Obviously, gitk, Rietveld et al. seem
> to use 8 spaces per tab.
I've just committed a patch that converts tabs to spaces in al
Werner LEMBERG wrote
> Yes, and avoiding overlaps everywhere would lead to unnecessarily
> complicated code. Tools like FontForge should be used to fix this in
> a post-processing stage, exactly as we do.
I totally agree. I'm going to fix the cases giving an error.
"Don't fix it if it ain't broke
> Unfortunately, mf overlaps can hardly be avoided in many cases,
> because lots of glyphs are being composed out of several overlapping
> predefined components.
Yes, and avoiding overlaps everywhere would lead to unnecessarily
complicated code. Tools like FontForge should be used to fix this i
Sorry, my "turn" was a goof: The loop in the outline produced a tiny
fissure…
Now I've put a bit more effort in it, combining two subpaths at their
intersection so that metapost's output will be a plain and simple outline,
/exactly/ matching the original turn outline, but without any loops or
ove
Werner LEMBERG wrote
> The output produced by the `mf2pt1` script to convert METAFONT input files
> to Type1 PostScript fonts often contains overlapping glyphs. This should
> be
> avoided in general.[1] For this reason, `mf2pt1` by default calls
> `FontForge` in batch mode to remove overlaps.
He
Some time ago I was asked to document how to prepare MWE for reporting
FontForge problems with Emmentaler. Here it is.
How to report `FontForge` problems while creating LilyPond fonts
The output produced by the `mf2pt1` script
