Ar 07/02/2005 am 10:45, ysgrifennodd George Williams: > On Sat, 2005-01-29, someone wrote > > Also note that there're two modes of copying in FontForge: with > > metrics, or just glyph outlines (without metrics). For all of these > > glyphs, you want to copy metrics over as well. I don't know how this > > is exactly done from scripts, but there's a "Copy metadata" in the > > Edit menu somewhere, which modifies the basic copying behaviour in UI. > > Perhaps Copy() works this way from scripts by default. > Copy metadata isn't apropos here. That copies glyph-names & unicode code > point as well as outlines. > > Whether the advance width is copied (I assume that's what is meant by > "with metrics") depends on whether you do a Paste() which clears out the > old glyph (if any) and replaces it with the new. This copies the advance > width too. Or PasteInto() which adds the outlines in the clipboard to > the destination glyph (and leaves the previous stuff there). This does > not change the advance width.
Right, Paste() is what I've been using, and I gather from what you say that it's what's appropriate for this situation. > On Thu, 2005-02-03 at 14:38, Dafydd Harries wrote: > > The results are mostly successful, but there are some problems with the > > sizes (metrics?) of some glyphs in some of the fonts, which aren't > > present in the fonts I copied them from. > I don't understand what you are saying. When ff copies a glyph from one > font to another it should not change it in any way. If you copy a glyph > into a mono-space font it will not be adjusted to fit. If you copy a > glyph into a font with a different em-size, cap-height, x-height, etc. > it will not be adjusted to fit. Aha, perhaps these adjustments need to be made in some cases, if the em-size or some other parameter different between the two version of the fonts. It seems to me that this might not be something that can be automated, though. If they are different, it's odd that the problem has somehow happened in the first place. > Similarly copying a glyph should not change any other glyphs (except for > those which refer to the copied glyph) > > If you have a glyph that has been changed by the copying process, that > is a bug in fontforge. > > But I don't know enough about how the glyphs in > http://kvota.net/fonts/urwcyr/nimbus-mono-side-by-side.png > were generated to tell what's going on. I think 271427 is saying that > this bug has nothing to do with the copying you've done and is a > separate issue? Shouldn't you just copy the glyphs from Valek's fonts? Yes, it seems all of the remaining problems in the fonts were not introduced by my changes. Thanks for looking at this bug. -- Dafydd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
