Issue 33947 - Office does not handle TTE font for PUA rendering
Summary: Office does not handle TTE font for PUA rendering
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: 680m106
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 2.0.1
Assignee: stefan.baltzer
QA Contact: issues@gsl
Depends on:
Reported: 2004-09-08 05:37 UTC by naoyuki
Modified: 2006-04-14 07:08 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description naoyuki 2004-09-08 05:37:56 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;"                                            \
Comment 1 2004-09-09 15:19:03 UTC
Patch applied in CWS vcl27.
Comment 2 2004-09-20 10:17:11 UTC
reopening for rassignmet
Comment 3 2004-09-20 10:17:48 UTC
reassigning for verification
Comment 4 2004-09-20 10:24:39 UTC
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
Comment 5 stefan.baltzer 2004-10-01 13:39:11 UTC
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.
Comment 6 stefan.baltzer 2004-10-01 15:59:45 UTC
SBA->HDU: Above problem affects Linux only (OK on Win and Sols)
Comment 7 stefan.baltzer 2004-10-01 17:15:41 UTC
SBA-> HDU: As seen, it works on LINUX too. Reassigned to me.
Comment 8 stefan.baltzer 2004-10-01 17:16:00 UTC
set to fixed.
Comment 9 stefan.baltzer 2004-10-01 17:16:23 UTC
SBA: verified in CWS vcl27.
Comment 10 stefan.baltzer 2004-11-24 18:52:32 UTC
SBA: OK in 680m62. Closed.
Comment 11 stefan.baltzer 2004-11-24 19:04:45 UTC
SBA: OOops. Closed wrong issue. Reopen this one...
Comment 12 stefan.baltzer 2004-11-24 19:10:38 UTC
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).
Comment 13 2004-12-02 10:35:47 UTC
The sorting by quality of the glyph fallback fonts caused this new problem...
Comment 14 tora3 2005-07-22 18:07:05 UTC
 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.

 An existence of glyphs in the font StarSymbol seems to sabotage 
 the font fallback system on the recent 680s.

 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. 

 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
  perl -pe 's/arialunicodems;/eudc;unicodems;/' >
  strings | grep starsymbol

 will be substituted with

 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. 
Comment 15 tora3 2005-07-22 18:24:10 UTC
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/ to recognize the font name EUDC.

 To use it with StarSuite 8, remove glyphs from StarSymbol 
 that conflict with glyphs in EUDC.ttf.
Comment 16 2005-07-25 13:57:28 UTC
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...
Comment 17 2005-08-24 15:06:55 UTC
Fixed in CWS vcl43 (assuming the problem is the one introduced in 680m62)
Comment 18 2005-09-02 15:36:18 UTC
HDU->SBA: please verify in CWS vcl43

re-open issue and reassign to sba
Comment 19 2005-09-02 15:36:23 UTC
reassign to sba
Comment 20 2005-09-02 15:36:27 UTC
reset resolution to FIXED
Comment 21 stefan.baltzer 2005-10-26 14:11:39 UTC
SBA: Verified in CWS vcl43.
Comment 22 stefan.baltzer 2006-04-07 17:06:45 UTC
SBA-Naoyuki: Please re-verify in current version and close. Thank you.
Comment 23 naoyuki 2006-04-14 07:08:04 UTC
verified EUDC glyphs are displayed for PUA area code not StarSymbol glyphs when
selecting fonts other than StarSymbol with 2.0.2. Close.