You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
(5) |
Apr
(8) |
May
(41) |
Jun
(7) |
Jul
(7) |
Aug
(13) |
Sep
(5) |
Oct
(10) |
Nov
(25) |
Dec
(27) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(25) |
Feb
(6) |
Mar
(32) |
Apr
(33) |
May
(26) |
Jun
(50) |
Jul
(36) |
Aug
(28) |
Sep
(34) |
Oct
(18) |
Nov
(20) |
Dec
(38) |
2006 |
Jan
(38) |
Feb
(39) |
Mar
(26) |
Apr
(57) |
May
(17) |
Jun
(17) |
Jul
(38) |
Aug
(53) |
Sep
(95) |
Oct
(44) |
Nov
(26) |
Dec
(31) |
2007 |
Jan
(55) |
Feb
(82) |
Mar
(57) |
Apr
(45) |
May
(23) |
Jun
(46) |
Jul
(58) |
Aug
(45) |
Sep
(74) |
Oct
(96) |
Nov
(35) |
Dec
(13) |
2008 |
Jan
(106) |
Feb
(55) |
Mar
(54) |
Apr
(38) |
May
(43) |
Jun
(79) |
Jul
(67) |
Aug
(55) |
Sep
(36) |
Oct
(62) |
Nov
(135) |
Dec
(69) |
2009 |
Jan
(67) |
Feb
(86) |
Mar
(33) |
Apr
(25) |
May
(41) |
Jun
(44) |
Jul
(25) |
Aug
(70) |
Sep
(74) |
Oct
(30) |
Nov
(32) |
Dec
(33) |
2010 |
Jan
(30) |
Feb
(9) |
Mar
(22) |
Apr
(85) |
May
(35) |
Jun
(35) |
Jul
(29) |
Aug
(23) |
Sep
(77) |
Oct
(13) |
Nov
(21) |
Dec
(9) |
2011 |
Jan
(3) |
Feb
(49) |
Mar
(91) |
Apr
(19) |
May
(40) |
Jun
(12) |
Jul
(27) |
Aug
(45) |
Sep
(21) |
Oct
(30) |
Nov
(14) |
Dec
(8) |
2012 |
Jan
(48) |
Feb
(56) |
Mar
(10) |
Apr
(30) |
May
(35) |
Jun
(51) |
Jul
(27) |
Aug
(154) |
Sep
(48) |
Oct
(39) |
Nov
(10) |
Dec
(52) |
2013 |
Jan
(56) |
Feb
(38) |
Mar
(26) |
Apr
(58) |
May
(23) |
Jun
(85) |
Jul
(15) |
Aug
(23) |
Sep
(89) |
Oct
(32) |
Nov
(23) |
Dec
(82) |
2014 |
Jan
(21) |
Feb
(15) |
Mar
(38) |
Apr
(9) |
May
(25) |
Jun
(16) |
Jul
(8) |
Aug
(49) |
Sep
(27) |
Oct
(26) |
Nov
(43) |
Dec
(4) |
2015 |
Jan
(21) |
Feb
(15) |
Mar
(62) |
Apr
(13) |
May
(8) |
Jun
(12) |
Jul
(12) |
Aug
(15) |
Sep
(41) |
Oct
(7) |
Nov
(30) |
Dec
(11) |
2016 |
Jan
(17) |
Feb
(28) |
Mar
(3) |
Apr
(8) |
May
(38) |
Jun
(13) |
Jul
(7) |
Aug
(45) |
Sep
(38) |
Oct
(7) |
Nov
(15) |
Dec
(20) |
2017 |
Jan
(17) |
Feb
(35) |
Mar
(34) |
Apr
(32) |
May
(47) |
Jun
(14) |
Jul
(48) |
Aug
(47) |
Sep
(15) |
Oct
(6) |
Nov
(2) |
Dec
(22) |
2018 |
Jan
(18) |
Feb
(3) |
Mar
(11) |
Apr
(6) |
May
(5) |
Jun
(11) |
Jul
(10) |
Aug
(1) |
Sep
(4) |
Oct
(6) |
Nov
(16) |
Dec
(26) |
2019 |
Jan
(50) |
Feb
(2) |
Mar
(42) |
Apr
(48) |
May
(21) |
Jun
(23) |
Jul
(39) |
Aug
(31) |
Sep
(11) |
Oct
(12) |
Nov
(22) |
Dec
(29) |
2020 |
Jan
(39) |
Feb
(25) |
Mar
(11) |
Apr
(24) |
May
(23) |
Jun
(21) |
Jul
(2) |
Aug
(2) |
Sep
(14) |
Oct
(18) |
Nov
(12) |
Dec
(15) |
2021 |
Jan
(1) |
Feb
(1) |
Mar
(10) |
Apr
(14) |
May
(3) |
Jun
(4) |
Jul
(4) |
Aug
|
Sep
(15) |
Oct
(7) |
Nov
(24) |
Dec
(2) |
2022 |
Jan
(4) |
Feb
(6) |
Mar
(1) |
Apr
(7) |
May
|
Jun
(1) |
Jul
|
Aug
(18) |
Sep
(6) |
Oct
(9) |
Nov
(1) |
Dec
(23) |
2023 |
Jan
(4) |
Feb
|
Mar
(39) |
Apr
|
May
|
Jun
|
Jul
(12) |
Aug
(8) |
Sep
(5) |
Oct
(2) |
Nov
(13) |
Dec
(4) |
2024 |
Jan
(10) |
Feb
(1) |
Mar
(5) |
Apr
(1) |
May
|
Jun
(3) |
Jul
|
Aug
(8) |
Sep
(20) |
Oct
|
Nov
|
Dec
|
From: Adrian H. <adr...@ar...> - 2008-03-16 03:23:27
|
Hi Folks — this is a simple "how to" question. I have an older style type 1 font which has the smallcaps in a separate font file. The encoding on this file is such that the smallcap a is simply called 'a', and so on. So that if, in the olden days, the user wanted the small caps then he would just switch to that font and type away. All well and good. But this presents problems now when I want to merge these small caps in with the main font (which I've successfully converted to open type). I clearly need to batch rename some glyphs and then do a merge. How do I batch rename them? I should mention that my first attempt at this failed. I renamed the lowercase letters only — 'a' to 'a.small' etc — and merged and defined the substitutions in the Lookup table, only to find that the spacing with the capital letters was screwed up. Clearly the capitals needed to be renamed and merged as well. Second simple question: Can I get the opentype logo in an otf font in Font Forge? Apparently one can get it by entering under the DSIG header usNumSigs (Number of signatures in the table) = 0; But I can't find a dialogue box for this. many thanks Adrian Heathcote |
From: George W. <gw...@si...> - 2008-03-14 22:24:03
|
On Fri, 2008-03-14 at 04:24, Benct Philip Jonsson wrote: > How do i move or remove guidelines created by dragging > from the rulers? Same way you remove guidelines created any other way: Go to the layers pane, select them, and delete them. The march 2 build had a bug in this, the march 9 build fixed it. |
From: Roger S. <rsp...@gm...> - 2008-03-14 18:22:42
|
A month or so ago, I installed andLinux on my Windows XP laptop. The installation process was trivial and took a few minutes only. Cygwin does seem to have its idiosyncracies, whereas andLinux seems to be uncomplicated Linux, except without a desktop. (Ubuntu, as it happens.) Since I require andLinux for development work I'm doing, I used Synaptic to install fontforge and fontforge-docs on my WinXP machine under andLinux. Unfortunately, I then discovered that Ubuntu is distributing fontforge version 20070607. I couldn't figure out how to convert the 20080309 rpm into a deb file, so I poked around and saw that the Debian unstable repository had Fontforge version 20080203. So I added that to Synaptic and installed this later version. The installation was effortless, as you might imagine. it may be only a subjective observation, but Fontforge seems a little faster under andLinux. (Most apps are reported to be faster.) More significantly,I now have access to the Spiro tools and can explore that approach to drawing curves. (Anything that promises a simpler approach to such matters attracts my interest. :-) I haven't had opportunity to stress this installation, but preliminarily I can report no problems. (I will report back if I do encounter problems.) If this continues to perform so smoothly, I will be kissing Cygwin goodbye. i urge other Windows-based users to investigate this alternative installation. Roger Sperberg -- rsperberg at gmail.com Cambodian Language Exercises -- cambodian.tiddlyspot.com Beginning Cambodian Reader -- cambodian-reader.tiddlyspot.com Modern Spoken Cambodian -- spokencambodian.110mb.com Click SEAlang add-on for Firefox -- sealang.net/download/ |
From: Benct P. J. <bp...@me...> - 2008-03-14 14:34:22
|
Benct Philip Jonsson skrev: > How do i move or remove guidelines created by dragging > from the rulers? OK found it |
From: Benct P. J. <bp...@me...> - 2008-03-14 12:24:43
|
How do i move or remove guidelines created by dragging from the rulers? /BP 8^)> -- Benct Philip Jonsson -- melroch atte melroch dotte se ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Sometimes you can't make it The best you can do is to fake it" (U2) |
From: George W. <gw...@si...> - 2008-03-14 01:31:40
|
On Thu, 2008-03-13 at 05:26, Roger Sperberg wrote: > Since the documentation is distributed now as a bz2 file, shouldn't > the extension be changed in the instructions here? And, more > significantly, shouldn't the third line read > > # tar xfj fontforge_htdocs*.bz2 > > Not being a Linux user (and currently running Fontforge under Cygwin), > I puzzled over this for a while. Yup. Fixed. |
From: Roger S. <rsp...@gm...> - 2008-03-13 13:30:39
|
As noted in previous posts to this list, I run Fontforge under Cygwin. For developmental work on the Nokia internet tablet, I am using andLinux to run Scratchbox and the Maemo SDK. Before I try installing Fontforge in andLinux, I was wondering if anyone on this list has tried this already and if they can give me any advice on what to watch out for. Thanks, Roger Sperberg -- firstinitial lastname at gmail.com Cambodian Language Exercises -- cambodian.tiddlyspot.com Beginning Cambodian Reader -- cambodian-reader.tiddlyspot.com Modern Spoken Cambodian -- spokencambodian.110mb.com Click SEAlang add-on for Firefox -- sealang.net/download/ |
From: Roger S. <rsp...@gm...> - 2008-03-13 13:26:11
|
I note that the documentation tarball is currently called fontforge_htdocs- 20080302.tar.bz2 The online instructions read thusly: Installing a documentation tarball Once you have downloaded the documentation tarball as described above, you should move to the directory containing it, and type: $ su password: ****** # mkdir -p /usr/local/share/doc/fontforge # mv fontforge_htdocs*.tgz /usr/local/share/doc/fontforge # tar xfz fontforge_htdocs*.tgz # rm fontforge_htdocs*.tgz Since the documentation is distributed now as a bz2 file, shouldn't the extension be changed in the instructions here? And, more significantly, shouldn't the third line read # tar xfj fontforge_htdocs*.bz2 Not being a Linux user (and currently running Fontforge under Cygwin), I puzzled over this for a while. Thanks, Roger Sperberg -- firstinitial lastname at gmail.com Cambodian Language Exercises -- cambodian.tiddlyspot.com Beginning Cambodian Reader -- cambodian-reader.tiddlyspot.com Modern Spoken Cambodian -- spokencambodian.110mb.com Click SEAlang add-on for Firefox -- sealang.net/download/ |
From: George W. <gw...@si...> - 2008-03-12 23:38:36
|
On Wed, 2008-03-12 at 05:53, Matthew Wallis wrote: > There seems to be a problem in the latest version with generating CID > fonts. They are a fraction of the size they should be and don't seem > to contain any glyphs. It is dumping the background layer by mistake. |
From: George W. <gw...@si...> - 2008-03-12 21:13:26
|
On Wed, 2008-03-12 at 04:36, Benct Philip Jonsson wrote: > Can someone please help me with a script to move every > character of a font to a codepoint which is a specified > number of codepoints higher? E.g. 0x0020 moves to 0xe000 > 0x0021 moves to 0xe001 and so on. The idea is to move > legacy custom fonts into the PUA without changing the > relative position of characters within a block. I typically > don't want to move the first 32 or first 128 characters, so > it must be possible to specify a starting position. I've > found cut'n'paste to be error-prone, so I hope this can be > done by scripting. Cut and paste certainly seems to be the way I would approach the problem. You don't mention what errors you had. The only thing I can think of is that your references would continue to point into the 32-128 area. That's easy to fix. Simply Unlink references first, then cut/paste then regenerate them afterward. |
From: Benct P. J. <bp...@me...> - 2008-03-12 12:36:58
|
Can someone please help me with a script to move every character of a font to a codepoint which is a specified number of codepoints higher? E.g. 0x0020 moves to 0xe000 0x0021 moves to 0xe001 and so on. The idea is to move legacy custom fonts into the PUA without changing the relative position of characters within a block. I typically don't want to move the first 32 or first 128 characters, so it must be possible to specify a starting position. I've found cut'n'paste to be error-prone, so I hope this can be done by scripting. /BP 8^)> -- Benct Philip Jonsson -- melroch atte melroch dotte se ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Sometimes you can't make it The best you can do is to fake it" (U2) |
From: George W. <gw...@si...> - 2008-03-09 22:47:55
|
On Sat, 2008-03-08 at 04:00, Christopher Fynn wrote: > Denis Jacquerye wrote: > > > In theory the solution would be to use the OpenType BASE > > table. But support for writing and reading that table is rather > > absent. That table allows to set different linheights per script or > > language. > > Would be nice if FontForge had support for BASE table allowing us to specify > different baselines (and different types of baseline) for different scripts. If you are volunteering to add support for the BASE table to fontforge, please feel free. |
From: George W. <gw...@si...> - 2008-03-09 20:22:16
|
On Sat, 2008-03-08 at 08:29, David McCann wrote: > I've just upgraded to Fedora 8 and so had to re-install FontForge. When > I tried to use the latest RPM, I got an error message that it couldn't > install because it needed /usr/bin/fontforge which (not surprisingly) I > hadn't got. Very odd. The rpm installs /usr/bin/fontforge. There should be no dependency on it. There is no /usr/bin/fontforge on the build machine. On my RedHat 9.0 system the rpm installs successfully. I don't think I can help you. |
From: David M. <da...@po...> - 2008-03-08 16:27:59
|
I've just upgraded to Fedora 8 and so had to re-install FontForge. When I tried to use the latest RPM, I got an error message that it couldn't install because it needed /usr/bin/fontforge which (not surprisingly) I hadn't got. Luckily the source compiled and installed OK, after I'd sat with my fingers crossed for 15 minutes. |
From: Christopher F. <cf...@gm...> - 2008-03-08 12:00:13
|
Denis Jacquerye wrote: > In theory the solution would be to use the OpenType BASE > table. But support for writing and reading that table is rather > absent. That table allows to set different linheights per script or > language. Would be nice if FontForge had support for BASE table allowing us to specify different baselines (and different types of baseline) for different scripts. If there were a few fonts with such entries in the BASE table then perhaps Pango, application developers, etc might be encouraged to support it. But I guess it is one of those chicken and egg situations - without support in layout engines there is no pressure to include in fonts. - Chris |
From: Peter B. <ps...@vi...> - 2008-03-07 13:23:06
|
Xgridfit, the "hinting" language for FontForge users crazy enough to work with TrueType fonts, has now reached release 1.5. New features include the ability to call a glyph program in the manner of a macro, complete with parameters (including a special "offset" parameter that is automatically added to all point numbers); a restore-default element for restoring graphics variables to their default state; and an alias element for accessing things (control-values, variables, etc.) under different names. People who use the program but don't need the new features should upgrade anyway, for a significant bug has been found and fixed, and this release contains various improvements and efficiencies. Peter http://xgridfit.sf.net/ |
From: Michel B. <bo...@ir...> - 2008-03-07 13:00:12
|
Michel Boyer wrote: > I just tried (without even generating a sfd) with a pfb+pfa font I have > correction: pfb + afm Michel |
From: Michel B. <bo...@ir...> - 2008-03-07 12:43:36
|
I just tried (without even generating a sfd) with a pfb+pfa font I have and I do not experience that problem. Of course, my XeLaTeX input file uses the unicode characters, not those we normally use in TeX (and that get replaced) i.e. my input is \documentclass{article} \usepackage{fontspec} \begin{document} \fontspec{myfont} “Here are double quotes” and ‘single quotes’ . \end{document} and the pdf generated is fine with single and double quotes nicely curved. Michel George Williams wrote: > On Wed, 2008-03-05 at 15:39, Adrian Heathcote wrote: > >> Hello — I've been trying to do something very simple in FontForge and >> it has not worked properly. I've been attempting to convert a >> postscript type 1 outline font to opentype. So opening up the file, >> saving as .sdf and then generating the fonts as .otf ought to do it. >> But I get a straight (vertical) quote mark (at U+0027, the apostrophe >> quote) instead of the curled quote marks which are at U+2018 and U >> +2019. >> > Um. This sounds more like a question to ask the XeTeX people. > > If there are glyphs at U+2018 and U+2019 then they will be used when > word processor asks for Unicode U+2018. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Fontforge-users mailing list > Fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-users > |
From: H <hi...@gm...> - 2008-03-07 06:46:09
|
In the name of huge sucess that we had for our techincal fest named Perizia, here is the one font so named which I made using fontforge and inkscape. The idea was to make a typographic design with asymmetric variations over the shape and width - a title which no one suggest for a tech fest. more and link to font at http://hiraneffects.blogspot.com/2008/03/thanks-perizia-is-now-font.html Great if suggestions are posted as blog comments. -- Cheers, H WARNING :The opinions expressed above are yours. They are not necessarily those of my employer or myself. hiraneffects.blogspot.com | 91.9846951870 | IRC Nick/ Freenode :HFactor [ c u @ #smc-project | #sugar | #python] |
From: George W. <gw...@si...> - 2008-03-07 04:32:32
|
On Wed, 2008-03-05 at 15:39, Adrian Heathcote wrote: > Hello — I've been trying to do something very simple in FontForge and > it has not worked properly. I've been attempting to convert a > postscript type 1 outline font to opentype. So opening up the file, > saving as .sdf and then generating the fonts as .otf ought to do it. > But I get a straight (vertical) quote mark (at U+0027, the apostrophe > quote) instead of the curled quote marks which are at U+2018 and U > +2019. Um. This sounds more like a question to ask the XeTeX people. If there are glyphs at U+2018 and U+2019 then they will be used when word processor asks for Unicode U+2018. |
From: Adrian H. <adr...@ar...> - 2008-03-06 08:49:18
|
My apologies. This seems to be a bug in XeLaTeX or the Fontspec interface. The Main defined font works correctly, but any subsidiary fonts seems not to know which language they are meant to work with, hence they do not make the correct punctuation replacements. I'll report this to the fontspec guy. Sorry to cause noise. Adrian |
From: Adrian H. <adr...@ar...> - 2008-03-05 23:39:08
|
Hello — I've been trying to do something very simple in FontForge and it has not worked properly. I've been attempting to convert a postscript type 1 outline font to opentype. So opening up the file, saving as .sdf and then generating the fonts as .otf ought to do it. But I get a straight (vertical) quote mark (at U+0027, the apostrophe quote) instead of the curled quote marks which are at U+2018 and U +2019. I have checked the .otf file and the latter two glyphs are present, as you'd expect, as are also the double curled quotes. But they do not appear in the document when I use the open type font under XeLaTeX, (nor under Text Edit, but that may have something to do with the program settings). I noticed that someone else had a similar problem a few days ago. I have discovered this problem with several font conversions. (I am using Mac OSX 10.4.11.) Bought opentype fonts do not exhibit this problem. Could this be a bug? Or is it the result of my incompetence somewhere in the conversion process. many thanks for any assistance Adrian |
From: George W. <gw...@si...> - 2008-03-05 22:11:12
|
On Wed, 2008-03-05 at 10:04, Matthew Wallis wrote: > Thanks for the info. I worked around the problem by inserting the characters I wanted from CNS 1.5 into your CNS 1.4 cidmap file. > So what does Change Supplement actually do - is it just for > information purposes? No, it changes the supplement number stored in the font so that when you generate a CID font it will have the corrected supplement number. > FF won't rescan the font and update any glyph information according to > the newer supplement? That is correct. If the font is released with an old supplement number then it should only have the glyphs pertaining to that supplement, so rescanning should not be needed. New glyphs will be added with the information from the new supplement. I presume you used it because ff only found supplement 4 when loading a font released with supplement 5. That's not what the command means. |
From: Matthew W. <ma...@wo...> - 2008-03-05 18:09:29
|
Thanks for the info. I worked around the problem by inserting the characters I wanted from CNS 1.5 into your CNS 1.4 cidmap file. So what does Change Supplement actually do - is it just for information purposes? FF won't rescan the font and update any glyph information according to the newer supplement? -----Original Message----- From: George Williams [mailto:gw...@si...] Sent: 05 March 2008 16:16 To: Matthew Wallis Cc: fon...@li... Subject: Re: [Fontforge-users] cidmaps On Tue, 2008-03-04 at 09:52, Matthew Wallis wrote: > I'd like to get FF to use Adobe cmaps newer than those supplied, ie > CNS and GB 1.5 rather than 1.4. Is this something possible to do > fairly painlessly? Ah. I tend not to notice when Adobe releases new supplements. I've updated the versions in the cvs tree, so you can pull down current ones from there. > When it says in the docs "There are also many other character sets > floating around feel free to install them yourself", is that referring > to cmap or cidmap files, No, that section is talking about standard encodings. > or are they the same (they don't seem to be)? They aren't. > And how do you install them? Which? Encodings? Find an encoding file and say Encoding->Load Encoding Or if it's an encoding known to iconv Encoding->Add Encoding Name... > If with a CID font open, I do Change Supplement, then do search, and > select an Adobe cmap file, FF crashes. I cannot repeat this. In my tests it happily changes the supplement. Please explain exactly what you did and what system you are using. > (In any case, would it update glyph information that way? Wouldn't it > be better if it was using the newer cmap when it opened the font?) ? No. If a font says it uses supplement 4 then it is probably better to use supplement 4. |
From: George W. <gw...@si...> - 2008-03-05 16:15:25
|
On Tue, 2008-03-04 at 09:52, Matthew Wallis wrote: > I'd like to get FF to use Adobe cmaps newer than those supplied, ie > CNS and GB 1.5 rather than 1.4. Is this something possible to do > fairly painlessly? Ah. I tend not to notice when Adobe releases new supplements. I've updated the versions in the cvs tree, so you can pull down current ones from there. > When it says in the docs "There are also many other character sets > floating around feel free to install them yourself", is that referring > to cmap or cidmap files, No, that section is talking about standard encodings. > or are they the same (they don't seem to be)? They aren't. > And how do you install them? Which? Encodings? Find an encoding file and say Encoding->Load Encoding Or if it's an encoding known to iconv Encoding->Add Encoding Name... > If with a CID font open, I do Change Supplement, then do search, and > select an Adobe cmap file, FF crashes. I cannot repeat this. In my tests it happily changes the supplement. Please explain exactly what you did and what system you are using. > (In any case, would it update glyph information that way? Wouldn't it > be better if it was using the newer cmap when it opened the font?) ? No. If a font says it uses supplement 4 then it is probably better to use supplement 4. |