<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: One Bit</title>
	<atom:link href="http://www.mondaynote.com/2009/10/19/one-bit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mondaynote.com/2009/10/19/one-bit/</link>
	<description>Media, Tech &#38; Business Models</description>
	<lastBuildDate>Wed, 19 Jun 2013 08:40:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: ranggaw0636</title>
		<link>http://www.mondaynote.com/2009/10/19/one-bit/#comment-5361</link>
		<dc:creator>ranggaw0636</dc:creator>
		<pubDate>Wed, 21 Jul 2010 14:56:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2150#comment-5361</guid>
		<description>@roy
but it&#039;s not better</description>
		<content:encoded><![CDATA[<p>@roy<br />
but it&#8217;s not better</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: roy</title>
		<link>http://www.mondaynote.com/2009/10/19/one-bit/#comment-5351</link>
		<dc:creator>roy</dc:creator>
		<pubDate>Wed, 21 Jul 2010 08:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2150#comment-5351</guid>
		<description>i have use it, it&#039;s more cool than vista</description>
		<content:encoded><![CDATA[<p>i have use it, it&#8217;s more cool than vista</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fajar</title>
		<link>http://www.mondaynote.com/2009/10/19/one-bit/#comment-4874</link>
		<dc:creator>fajar</dc:creator>
		<pubDate>Mon, 12 Jul 2010 02:17:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2150#comment-4874</guid>
		<description>Thank you for the link</description>
		<content:encoded><![CDATA[<p>Thank you for the link</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik Holmegaard</title>
		<link>http://www.mondaynote.com/2009/10/19/one-bit/#comment-1517</link>
		<dc:creator>Henrik Holmegaard</dc:creator>
		<pubDate>Mon, 19 Oct 2009 14:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2150#comment-1517</guid>
		<description>Dear Jean-Louis,

Adobe PDF 1.3 is not searchable for conventional book composition. Please, check for yourself. More then half the glyphs in an intelligent font file, beginning with Apple Hoefler Text introduced at the Apple World Wide Developer Conference in May 1992, has GID Glyph Identifiers and no CID Character Identifiers (UTF16, UTF8, long character identifiers). Only glyphs that have both GIDs and CIDs stay searchable (that is, they are drawn by the obligatory CMAP Character Map in the TrueType Specification).

Mac OS 7.5 in September 1994 introduced drawing of typographic ligatures, typographic small capitals, typographic superscripts, typographic subscripts and more without chaotifyng the source character string. Searching, spelling, and sorting have worked for a decade and a half no matter how complex the composition. In the Apple TrueType 2 model first demonstrated at the World Wide Developer Conference in May 1992, character codes are public and font-independent while glyph codes are private and font-dependent. This is also the model in Microsoft&#039;s additions to TrueType, first named TrueType Open and then named OpenType.

Meanwhile,Apple is selling a million Macs a month, and it is easier to do so if as well the simple CMAP shaping as the supplementary Apple MORT/MORX and Microsoft GSUB shaping is supported in authoring applications that depend on system level services. The everyday enduser perceives Apple Mac OS X as a platform for advanced typography, but if the supplementary Apple MORT/MORX and Microsoft GSUB shaping is not searchable in PDF 1.3, and if the enduser is not told, then this is not moral marketing. 

Microsoft Word for Macintosh 2008 only allows access to modern / common typographic ligatures in intelligent font files, only as a global on/off setting, and the setting is off by default. Apple iWork allows access to any supplementary shaping in the intelligent font file through the Apple Typography Palette, and modern / common typographic ligatures are on by default. There is therefore a proportionally higher loss of character information.

Unfortunately, if document descriptions do not perish in the memory of the printing system as the printed paper emerges, but persist on disk, then they must maintain the source character string as the style runs in the intelligent font file, and that is not happening for the supplementary shaping. The Type 42 Specification introduced in 1993 makes it legal to strip all tags except the font program tags, that is, the spline drawings. Thus the core of the intelligent font file format, the CMAP Character Map, may be stripped. The intact ICC tagged file format  can be saved into PDF 1.3, but the intact SFNT Spline Font file format can first be saved in PDF 1.6, in Adobe PDFXML (Adobe Mars), and in Microsoft XPS.


Best wishes,
Henrik Holmegaard
would-be technical writer

Reference:
http://www.planetpdf.com/enterprise/article.asp?ContentID=6521

To see potential problems with products that support advanced typography features, such as ligatures, small caps and old-style numerals, see the Adobe OpenType User Guide, authored with Adobe InDesign and exported directly to PDF:

&quot;2002&quot; is present in the first page below the title -- but cannot be located as since old-style figures are used.
The SFNT acronym present in the first paragraph in page 2 cannot be located, as it uses small-caps.
&quot;Microsoft&quot; is present 5 times in this document -- but none of the instances can be located due to the use of ligatures (ft in this case). Even the word &quot;This&quot; in the opening paragraph in page 2 (line before last) cannot be located due to the use of ligatures. The more common fi, fl, ffi ligatures are searchable in the case of this document, but this is not the case in other documents using these ligatures (this depends on the applications used to author/create the PDF).
While these OpenType features result in a superior typography, they should be avoided in online documents, until Acrobat Find and Search functions are enhanced to support the additional characters.

As an example for a PDF with text that is internally deformed, see the Adobe InDesign Programming Guide. It includes numerous code fragments (see pages 419 and onwards) set in a monospace font, and the same font is used in regular text to indicate function names or related items. All of these are not searchable. Copy and paste the text and you&#039;ll see why: &quot;matrix passed&quot; is understood internally as &quot;2#___A&quot;.#%%_&amp;&quot;&quot;. With this type of document, users could have happily used the copy and paste function to reduce typing time/errors when studying or implementing the techniques discussed, but results in this case are of no value.</description>
		<content:encoded><![CDATA[<p>Dear Jean-Louis,</p>
<p>Adobe PDF 1.3 is not searchable for conventional book composition. Please, check for yourself. More then half the glyphs in an intelligent font file, beginning with Apple Hoefler Text introduced at the Apple World Wide Developer Conference in May 1992, has GID Glyph Identifiers and no CID Character Identifiers (UTF16, UTF8, long character identifiers). Only glyphs that have both GIDs and CIDs stay searchable (that is, they are drawn by the obligatory CMAP Character Map in the TrueType Specification).</p>
<p>Mac OS 7.5 in September 1994 introduced drawing of typographic ligatures, typographic small capitals, typographic superscripts, typographic subscripts and more without chaotifyng the source character string. Searching, spelling, and sorting have worked for a decade and a half no matter how complex the composition. In the Apple TrueType 2 model first demonstrated at the World Wide Developer Conference in May 1992, character codes are public and font-independent while glyph codes are private and font-dependent. This is also the model in Microsoft&#8217;s additions to TrueType, first named TrueType Open and then named OpenType.</p>
<p>Meanwhile,Apple is selling a million Macs a month, and it is easier to do so if as well the simple CMAP shaping as the supplementary Apple MORT/MORX and Microsoft GSUB shaping is supported in authoring applications that depend on system level services. The everyday enduser perceives Apple Mac OS X as a platform for advanced typography, but if the supplementary Apple MORT/MORX and Microsoft GSUB shaping is not searchable in PDF 1.3, and if the enduser is not told, then this is not moral marketing. </p>
<p>Microsoft Word for Macintosh 2008 only allows access to modern / common typographic ligatures in intelligent font files, only as a global on/off setting, and the setting is off by default. Apple iWork allows access to any supplementary shaping in the intelligent font file through the Apple Typography Palette, and modern / common typographic ligatures are on by default. There is therefore a proportionally higher loss of character information.</p>
<p>Unfortunately, if document descriptions do not perish in the memory of the printing system as the printed paper emerges, but persist on disk, then they must maintain the source character string as the style runs in the intelligent font file, and that is not happening for the supplementary shaping. The Type 42 Specification introduced in 1993 makes it legal to strip all tags except the font program tags, that is, the spline drawings. Thus the core of the intelligent font file format, the CMAP Character Map, may be stripped. The intact ICC tagged file format  can be saved into PDF 1.3, but the intact SFNT Spline Font file format can first be saved in PDF 1.6, in Adobe PDFXML (Adobe Mars), and in Microsoft XPS.</p>
<p>Best wishes,<br />
Henrik Holmegaard<br />
would-be technical writer</p>
<p>Reference:<br />
<a href="http://www.planetpdf.com/enterprise/article.asp?ContentID=6521" rel="nofollow">http://www.planetpdf.com/enterprise/article.asp?ContentID=6521</a></p>
<p>To see potential problems with products that support advanced typography features, such as ligatures, small caps and old-style numerals, see the Adobe OpenType User Guide, authored with Adobe InDesign and exported directly to PDF:</p>
<p>&#8220;2002&#8243; is present in the first page below the title &#8212; but cannot be located as since old-style figures are used.<br />
The SFNT acronym present in the first paragraph in page 2 cannot be located, as it uses small-caps.<br />
&#8220;Microsoft&#8221; is present 5 times in this document &#8212; but none of the instances can be located due to the use of ligatures (ft in this case). Even the word &#8220;This&#8221; in the opening paragraph in page 2 (line before last) cannot be located due to the use of ligatures. The more common fi, fl, ffi ligatures are searchable in the case of this document, but this is not the case in other documents using these ligatures (this depends on the applications used to author/create the PDF).<br />
While these OpenType features result in a superior typography, they should be avoided in online documents, until Acrobat Find and Search functions are enhanced to support the additional characters.</p>
<p>As an example for a PDF with text that is internally deformed, see the Adobe InDesign Programming Guide. It includes numerous code fragments (see pages 419 and onwards) set in a monospace font, and the same font is used in regular text to indicate function names or related items. All of these are not searchable. Copy and paste the text and you&#8217;ll see why: &#8220;matrix passed&#8221; is understood internally as &#8220;2#___A&#8221;.#%%_&amp;&#8221;". With this type of document, users could have happily used the copy and paste function to reduce typing time/errors when studying or implementing the techniques discussed, but results in this case are of no value.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simon</title>
		<link>http://www.mondaynote.com/2009/10/19/one-bit/#comment-1515</link>
		<dc:creator>simon</dc:creator>
		<pubDate>Mon, 19 Oct 2009 09:51:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2150#comment-1515</guid>
		<description>good thinking Bruce Wayne. It&#039;s all coming together, bit by bit. In that inimitable Jobsian way......</description>
		<content:encoded><![CDATA[<p>good thinking Bruce Wayne. It&#8217;s all coming together, bit by bit. In that inimitable Jobsian way&#8230;&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
