https://issues.apache.org/bugzilla/show_bug.cgi?id=51413
Bug #: 51413
Summary: tag support to make section of rtf document readonly
Product: Fop
Version: 1.0
Platform: All
OS/Version: Windows XP
Status: NEW
Sever
I tested the latest code in the branch ComplexScripts with a font
called Lohit-Devanagari, version 2.4.5, copyright Red Hat, license
GPLv2, file lohit_hi.ttf, Debian package ttf-devanagari-fonts.
Fontforge shows that the font has 2 GPOS tables and a large number of
GSUB tables.
I was not successfu
Glenn,
I studied the OpenType spec. With that knowledge I assumed, perhaps
naively, that for all OT fonts a correct rendering can be obtained by
following the directives in the tables in the font.
The code of the ComplexScripts branch provides specific processing of
each Indic font (until now Dev
https://issues.apache.org/bugzilla/show_bug.cgi?id=49687
--- Comment #38 from Simon Pepping 2011-06-22 18:31:13
UTC ---
The code contains a number of Unicode properties, e.g. in util.CharUtilities
and DevanagariScriptProcessor. It would be better if all Unicode properties
would be collected in o
That is correct. Due to the design of OTF, the font tables are insufficient.
Each Indic script requires its own orthographic syllabization logic. Where
there is common logic, it will be shared in the implementation.
Arabic script has other script specific requirements outside of the font
tables. F
Microsoft changed the Indic script processing logic around 2008, and newer
fonts provide both old 'deva' (now deprecated) and new 'dev2' tables.
Apparently the older font you accessed does not. I have not tested against
older fonts that do not support the new 'dev2' semantics.
I have listed the fo
https://issues.apache.org/bugzilla/show_bug.cgi?id=49687
--- Comment #39 from Glenn Adams 2011-06-22 19:29:51 UTC ---
(In reply to comment #38)
> The code contains a number of Unicode properties, e.g. in util.CharUtilities
> and DevanagariScriptProcessor. It would be better if all Unicode proper
