Issue 105446 - Improper font replacement for 'selected text' with asian font
Summary: Improper font replacement for 'selected text' with asian font
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOO310m9
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
: 106414 (view as issue list)
Depends on:
Reported: 2009-09-29 12:46 UTC by yajva
Modified: 2017-05-20 11:22 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---

Illustrates buggy font rendering (11.14 KB, application/vnd.oasis.opendocument.text)
2009-09-29 12:47 UTC, yajva
no flags Details
Unicode Grantha font (844.27 KB, text/plain)
2009-09-29 12:50 UTC, yajva
no flags Details
Unicode Telugu font (190.97 KB, text/plain)
2009-09-29 12:51 UTC, yajva
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description yajva 2009-09-29 12:46:15 UTC
The attached file includes a sample asian text line with Telugu (Pothana2000
font), Grantha (e-Grantha font), and Kannada (Arial Unicode MS) scripts, all

Bug 1. Selecting the line and changing to a font which does not support the
script, instead of leaving the script alone, renders it into empty boxes.

Bug2. Arial Unicode MS glyphs don't change but the 'font name' combo displays
the new font name for these chars.

Bug3. Selecting a portion of text sandwiched between different scripts and
pasting into a text box renders  into empty boxes/circles
Comment 1 yajva 2009-09-29 12:47:47 UTC
Created attachment 65033 [details]
Illustrates buggy font rendering
Comment 2 yajva 2009-09-29 12:50:32 UTC
Created attachment 65034 [details]
Unicode Grantha  font
Comment 3 yajva 2009-09-29 12:51:10 UTC
Created attachment 65035 [details]
Unicode Telugu font
Comment 4 michael.ruess 2009-10-15 15:36:22 UTC
MRU->HDU: the font Pothana2000 seems to be incorrectly replaced. When it is not
installed on the system, the characters will all be displayed incorrectly.
This may be related to issue 99863.
Comment 5 michael.ruess 2009-10-29 09:56:38 UTC
*** Issue 106414 has been marked as a duplicate of this issue. ***
Comment 6 2009-11-05 11:09:45 UTC
Well, what is called "Bug 1" is an interesting enhancement request (for the WriterEngine and EditEngine). 
It is a good idea that needs a lot more consideration though: what should happen, when only 50% of 
the text can is supported by the newly selected font? Should it switch or not? All of the text or only the 
supported parts? Or should it bring up a dialog instead which outlines the problem and allows the user 
to reconsider what he really wants? Or should it just do what the user requested and change the font? 
The latter would be the status quo
This is all really tricky -> reassigning to the UX-team

What is called "Bug 2" is actually the same issue. You requested a font that does not support the 
selected text. The text now gets the requested new font attribute and that is shown in the fontname 
control. If the requested font does not support the script then it would be ok to display empty boxes 
instead. But is so smart that it recognizes the unicode codepoint as not being 
supported by the font. So it tries to use a different font to get something reasonable. If this different 
font is "Arial Unicode" as in your example then this feature kicking in is just what you are seeing.
Comment 7 yajva 2009-11-06 07:59:12 UTC

I quite agree with your observation on Bug1; I meant it's a bug in the sense of
what would be a more intuitive behavior.

In bug 2, I was trying to illustrate the point that the user is getting wrong
info regarding the fontname; the text rendering being one font and the combo
shows another. (Perhaps my reporting was not lucid enough.). Place the cursor at
the end of line consisting empty boxes (line 4). The combo shows the name as
Tahoma, while the redering is actually from Arial Unicode MS.
I hope I am clearer now.
Comment 8 yajva 2009-11-06 08:33:07 UTC
Following the remarks of hdu, I have submitted a clarification on 'bug2'.
Comment 9 eric.savary 2009-11-10 23:58:07 UTC
Reassigning as feature to HDU

@yajva: please remember: 1 problem = 1 issue. If you see different bugs, file
different issues. A grouped issue is invalid.
Comment 10 2009-11-11 07:45:16 UTC
> an interesting enhancement request (for the WriterEngine and EditEngine)

is still true, reassigning for WriterEngine. Feel free to clone this issue for EditEngine if this helps.
Comment 11 michael.ruess 2010-08-24 12:04:37 UTC
*** Issue 114082 has been marked as a duplicate of this issue. ***
Comment 12 Marcus 2017-05-20 11:22:46 UTC
Reset assigne to the default "".