Apache OpenOffice (AOO) Bugzilla – Issue 33947
Office does not handle TTE font for PUA rendering
Last modified: 2006-04-14 07:08:04 UTC
TTE font is TrueType font which contains PUA area glyphs and used with linking other fonts.(at least it's popular in Japanese market) Windows has the capability of handling this kind of fonts, although there is no standard way to handle this on *nix. Windows has the tool GaijiEditor which creates TTE fohts and many font vendors are selling TTE fonts as suppliment glyphs for standard system bundled TrueType fonts. I believe handling TTE fonts will need some amount of implementation and spec for configuration, so OOo2.0 timeframe is a little hard to achieve this. But minimum handling is easy and simple and it's very beneficial for some users. The EUDC (which is default fonts which Windows GaijiEditor creates) font can be used even on *nix with just copying that to OOo font dirs. Of course linking configuration will be needed for complete TTE suport, but it can be implemented later. 1. psprint/source/fontmanager/fontmanager.cxx *** fontmanager.cxx.orig Wed Sep 8 13:23:58 2004 --- fontmanager.cxx Wed Sep 8 13:25:07 2004 *************** *** 1301,1306 **** --- 1301,1307 ---- delete pFont; } else if( aExt.EqualsIgnoreCaseAscii( "ttf" ) + || aExt.EqualsIgnoreCaseAscii( "tte" ) || aExt.EqualsIgnoreCaseAscii( "otf" ) ) // #112957# allow GLYF-OTF { TrueTypeFontFile* pFont = new TrueTypeFontFile(); 2. vcl/source/gdi/outdev3.cxx *** outdev3.cxx.orig Wed Sep 8 13:25:57 2004 --- outdev3.cxx Mon Aug 30 17:26:22 2004 *************** *** 2901,2907 **** { // TODO: implement dynamic lists or improve static lists #define FALLBACKFONT_NAMELIST \ ! "arialunicodems;andalesansui;cyberbit;starsymbol;opensymbol;lucid\ atypewriter;" \ "msmincho;fzmingti;sunbatang;sundotum;baekmukdotum;" \ \ "hgmincholightj;msunglightsc;msunglighttc;hymyeongjolightk;" \ "lucidasans;tahoma;" \ --- 2901,2907 ---- { // TODO: implement dynamic lists or improve static lists #define FALLBACKFONT_NAMELIST \ ! "eudc;arialunicodems;andalesansui;cyberbit;starsymbol;opensymbol;\ lucidatypewriter;" \ "msmincho;fzmingti;sunbatang;sundotum;baekmukdotum;" \ \ "hgmincholightj;msunglightsc;msunglighttc;hymyeongjolightk;" \ "lucidasans;tahoma;" \
Patch applied in CWS vcl27.
reopening for rassignmet
reassigning for verification
HDU->SBA: please verify in CWS vcl27 on unx and win32 platforms. Testing instructions: - install the font EUDC.TTF (available in the bugdoc folder) - select some unicodes in the range U+E63E..U+E757 from this font - change the font for these symbols to another font, e.g. Andale => the symbols should be unchanged
SBA-> HDU: As seen, ALMOST verified in cws vcl27. Remaining problem: the .TTE font is not detected although it is in the /shre/fonts/truetype/ folder. It has to be renamed manually to *.TTF Reopened to reassign.
SBA->HDU: Above problem affects Linux only (OK on Win and Sols)
SBA-> HDU: As seen, it works on LINUX too. Reassigned to me.
set to fixed.
SBA: verified in CWS vcl27.
SBA: OK in 680m62. Closed.
SBA: OOops. Closed wrong issue. Reopen this one...
SBA->HDU: Does NOT work in 680m62. Renaming to .ttf doesn't help. When applying another font, the symbols get replaced with Korean characters (seen on my JDS).
The sorting by quality of the glyph fallback fonts caused this new problem...
Observation: The font fallback system seems not to work well on the build 680m106 while the same system in the build 645m52 (StarSuite 7 + PU4) works. Problem: An existence of glyphs in the font StarSymbol seems to sabotage the font fallback system on the recent 680s. Descriptions: (680m106) A font file EUDC.ttf, originally called EUDC.TTE, seems to work with build 680m106 if a font file starsymb.ttf for StarSymbol has been removed from share/fonts/truetype with spadmin. StarSymbol has glyphs in the same code range as EUDC.ttf occupies. Codes which have been token away from the font StarSymbol with a font file manipulation tool such as FontForge become to be displayed as a fallback font like EUDC. Those facts could imply that glyphs in the font StarSymbol is prior to glyphs in the other fallback fonts. (645m52) In the contrast to the build 680m106, StarSuite 7 PU4 bundled in Solaris 10 3/05 seems to work with the font fallback system. The following process lets StarSuite 7 recognize the font EUDC. cd /usr/starsuite7/program mv libvcl645si.so libvcl645si.so.saved perl -pe 's/arialunicodems;/eudc;unicodems;/' libvcl645si.so.saved > libvcl645si.so strings libvcl645si.so | grep starsymbol vcl/source/gdi/outdev3.cxx: arialunicodems;andalesansui;cyberbit;starsymbol;opensymbol;.... will be substituted with eudc;unicodems;andalesansui;cyberbit;starsymbol;opensymbol;.... Background: In the typical use, users assign one Japanese font name, e.g. HG-MinchoL-Sun, to both normal Japanese characters and End User Defined Characters. Please imagine that a single font name could be assigned to a cell which contains both types of characters on Calc. Migration from Windows PCs to Sun Ray terminals will definitely demand capability of handling End User Defined Characters.
Could you resume to take care of this issue? Many Japanese users have been waiting for this feature for a long time. Possible, Current, Workaround: To use EUDC.ttf with StarSuite 7, apply a patch to program/libvcl645si.so to recognize the font name EUDC. To use it with StarSuite 8, remove glyphs from StarSymbol that conflict with glyphs in EUDC.ttf.
Looking at the source history I think I found the candidate for this problem: Was the problem already in the first OOo2beta? If yes, then it was probably introduced in SRC680m62, which is about 8 months old...
Fixed in CWS vcl43 (assuming the problem is the one introduced in 680m62)
HDU->SBA: please verify in CWS vcl43 re-open issue and reassign to sba
reassign to sba
reset resolution to FIXED
SBA: Verified in CWS vcl43.
SBA-Naoyuki: Please re-verify in current version and close. Thank you.
verified EUDC glyphs are displayed for PUA area code not StarSymbol glyphs when selecting fonts other than StarSymbol with 2.0.2. Close.