Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators How to post technical questions? Post 302427150 by Neo on Friday 4th of June 2010 04:57:51 AM
Old 06-04-2010
Maybe the poster is asking what is the best way to post a technical question?

(1) Add as much detail as possible, for example OS and version, hardware if relevant, and other important details.

(2) Post output of log files, error messages, system commands, and other output that helps people understand your problem. Wrap this output in code tags or quote tags (code tags are generally used).

(3) Write a descriptive subject text. Do not post a question with subjects like "HELP ME! or "URGENT!"... or "GREP', etc. Take the time to create a subject that provides readers (and search engines) with something useful.

(4) Post in the correct forum. When in doubt, post in the "dummies" forum. OS specific questions should be posted in the same OS section.

(5) If you have written scripts or code, post that code in the forums wrapped in code tags. We need to see what you are doing and what you have tried.

(6) Do not post links to other web pages unless you have been around for a while. We delete spam very quickly here and you cannot self-promote here until you have shown a significant ability to contribute here. The forums are not a "fly-by-night place to post links to build your page rank.

What did I miss?
 

We Also Found This Discussion For You

1. Shell Programming and Scripting

Technical questions on bash,mysql and pHp

1. bash -bash escape rules, esp. ',", -how to use Ctrl+R reverse cmd search with regex? 2. mysql -how to use grep in mysql 3. php -why !0 is not evaluated to true? what's its value -php getopt: what if there is duplicate in cmdline args (2 Replies)
Discussion started by: John_Peter
2 Replies
Font::TTF::Post(3)					User Contributed Perl Documentation					Font::TTF::Post(3)

NAME
Font::TTF::Post - Holds the Postscript names for each glyph DESCRIPTION
Holds the postscript names for glyphs. Note that they are not held as an array, but as indexes into two lists. The first list is the standard Postscript name list defined by the TrueType standard. The second comes from the font directly. Looking up a glyph from a Postscript name or a name from a glyph number is achieved through methods rather than variable lookup. This class handles PostScript table types of 1, 2, 2.5 & 3, but not version 4. Support for version 2.5 is as per Apple spec rather than MS. The way to look up Postscript names or glyphs is: $pname = $f->{'post'}{'VAL'}[$gnum]; $gnum = $f->{'post'}{'STRINGS'}{$pname}; INSTANCE VARIABLES
Due to different systems having different limitations, there are various class variables available to control what post table types can be written. $Font::TTF::Post::no25 If set tells Font::TTF::Post::out to use table type 2 instead of 2.5 in case apps cannot handle version 2.5. VAL Contains an array indexed by glyph number of Postscript names. This is used when writing out a font. STRINGS An associative array of Postscript names mapping to the highest glyph with that name. These may not be in sync with VAL. In addition there are the standard introductory variables defined in the standard: FormatType italicAngle underlinePosition underlineThickness isFixedPitch minMemType42 maxMemType42 minMemType1 maxMemType1 METHODS
$t->read Reads the Postscript table into memory from disk $t->out($fh) Writes out a new Postscript name table from memory or copies from disk $t->XML_element($context, $depth, $key, $val) Outputs the names as one block of XML BUGS
o No support for type 4 tables AUTHOR
Martin Hosken Martin_Hosken@sil.org. See Font::TTF::Font for copyright and licensing. perl v5.16.3 2012-02-23 Font::TTF::Post(3)
All times are GMT -4. The time now is 11:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy