Thomas Henlich

Show:

What's happening?

  • Comment: UTF-8 support in PostScript driver

    Some fonts (e. g. Free UCS Outline Fonts) do not conform to Adobe's specification on glyph names (http://www.adobe.com/devnet/opentype/archives/glyph.html#6). Use this mapping table for ttf2pt1 to fix the glyph names for such fonts. File Added: aglfn.map.

    2007-07-05 13:02:48 UTC in gnuplot development

  • Comment: UTF-8 support in PostScript driver

    Cannot reproduce your bug with Dejavu Fonts 2.18 and Ghostscript 8.54. Are you sure you used the "-a" option to ttf2pt1? I also cannot follow your hypothesis about the glyph table (in the pfa file?) being too big. I know of no such restriction. The only restriction is the length of the encoding vector (is that what you were referring to?): 256. Since my patch uses the glyphshow operator...

    2007-07-03 06:33:56 UTC in gnuplot development

  • Comment: UTF-8 support in PostScript driver

    Additional description: With this patch, the PostScript driver supports all UTF-8 characters (the full range of Unicode) under the following conditions: - The font contains the required glyphs - The glyph names in the font follow Adobe's recommendation on glyph names: http://www.adobe.com/devnet/opentype/archives/glyph.html#6 As the standard 35 PS fonts do not contain a wide range of...

    2007-07-02 17:25:04 UTC in gnuplot development

  • UTF-8 support in PostScript driver

    Related to the discussion in patch [ 1734995 ] Extended PostScript Latin1 encoding vector, here is an experimental patch for UTF-8 support in the PostScript driver. It supports PostScript Type1 fonts which use glyph names according to the Adobe Glyph List For New Fonts.

    2007-07-02 09:19:01 UTC in gnuplot development

  • Comment: Extended PostScript Latin1 encoding vector

    Couldn't we just implement a "poor man's Unicode" PS driver which just stuffs the first 256 distinct characters from the output into a dynamically-generated encoding vector? This would probably cover 99% of gnuplot usage (it isn't a typesetting system, after all). Of course, there are better solutions, but this one is easy enough to implement and should be good enough for most users.

    2007-06-14 15:11:09 UTC in gnuplot development

  • Comment: Extended PostScript Latin1 encoding vector

    Why not simply call it 8859-1, just for historical reasons? It contains all characters from Latin1 in the same code positions, plus some more. Just as the original gnuplot 8859-1 encoding vector does. But I agree, a more correct name would be 'cp1252'. Since CP1252 is a superset of Latin1, that would actually make Latin1 superfluous. An even better solution would be Unicode support in...

    2007-06-12 12:11:28 UTC in gnuplot development

  • Comment: Extended PostScript Latin1 encoding vector

    File Added: gp-test.plt.

    2007-06-11 13:10:28 UTC in gnuplot development

  • Extended PostScript Latin1 encoding vector

    An PostScript encoding vector which is compatible to ISO-8859-1 and Windows Latin 1 (CP 1252). It also contains all the extra characters from MacRoman encoding (useful math symbols!) and some characters which are found in Y&Y Lucida Bright (dotlessj ff ffi ffl) The idea is borrowed from TeX Base 1 Encoding (8r). The code positions 00-1F were chosen to be compatible with some X11 bitmap...

    2007-06-11 13:08:23 UTC in gnuplot development

  • Location of wgnuplot.ini is documented incorrectly

    The documentation in section wgnuplot.ini states "Windows gnuplot will read some of its options from the [WGNUPLOT] section of WGNUPLOT.INI in the Windows directory." But this is incorrect, the location has changed from version 4.0 to the appdata directory.

    2007-06-08 08:44:00 UTC in gnuplot development

  • Illegal Postscript DSC comment with fontfile option

    When using the fontfile option, a comment "%BeginProcSet: ..." is written by the Postscript driver. The correct DSC comment would be: %%BeginProcSet (double percent signs)

    2007-06-07 18:33:44 UTC in gnuplot development

About Me


Send me a message