Issue 42735 - Should have separate font for each script as in Mozilla, instead of Western/Asian/CTL
Summary: Should have separate font for each script as in Mozilla, instead of Western/A...
Alias: None
Product: Internationalization
Classification: Code
Component: code (show other issues)
Version: 680m74
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: falko.tesch
QA Contact: issues@l10n
Keywords: oooqa
Depends on:
Blocks: 41707
  Show dependency tree
Reported: 2005-02-14 13:22 UTC by samphan
Modified: 2013-08-07 15:00 UTC (History)
8 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description samphan 2005-02-14 13:22:59 UTC
In Tools/Options/Language Settings/Languages, I can choose the default languages
for three types of script - Western, Asian, and CTL. Then in Format/Character
dialog box, I can set one font for 'Western text', one font for (East) 'Asian
text' and one font for 'CTL' (Bidi & Indic). I can also change the languages of
the three types of script to other languages than the default. 

However, if I want to make a document that consists of two CTL languages, e.g.
Thai and Lao, the mechanism will not work comfortably. Because I can't set
different fonts for Thai and Lao. I have to set them (the font and the language)
manually when I switch the language between Thai and Lao in the text. I may have
to do so because I have to use different fonts for Thai and Lao.

In Mozilla, they implement this differently. You can set separate font for each
script instead of just Western/Asian/CTL. This will make it easier to make
documents with mix languages.
Comment 1 pseudo_daoist 2005-02-16 01:03:47 UTC
>However, if I want to make a document that consists of two CTL languages, e.g.
Thai and Lao, the mechanism will not work comfortably.

a) A _good_ Unicode font makes that a non-issue.[I am not aware of any GNU GPL
Unicode fonts, that are good.   Code2000 is shareware, and covers most of
Unicode BMP. Code2001 covers Unicode Plane 1.  [OOo does not support Unicode
Plane 1 through 16.]

b) Creating, and using the appropriate paragraph, character, numbering, and cell
styles makes that a non-issue.  [Create a set of styles for each language, and
each writing system, if the language uses two or more writing systems.]


Comment 2 lists 2005-02-21 06:46:56 UTC
OOo has a file in which it is possible to define the favorite fonts for each locale.


You can see it in:

The issue would require a big change in font substitution strategy.

Please look at issue in
which I tried to define a new font substitution strategy for OOo writer... but
it was not defined on time to reach OOo 2.0.

Please see if this issue could be considered to be a duplicate of 31803.

Comment 3 arthit 2005-04-02 00:05:59 UTC
Comment 4 Martin Hollmichel 2005-05-22 07:34:28 UTC
set target to OOo Later.
Comment 5 falko.tesch 2005-10-20 20:56:18 UTC
FT: No, I disagree. This would clutter the UI waqy too much.
Comment 6 arthit 2005-10-21 10:15:31 UTC
I think we have to agree on the feature first, if it necessary or not.

If it is not, ok, "won't fix".

If it is necessary, do "fix".

And if we feel that it will not fit the current UI, .. change the UI, makes it fits.
Mozilla Seamonkey and Mozilla Firefox UI for choosing script's font is ok, imho.
OO.o may supports more scripts than Seamonkey/Firefox. But we can redesign the UI.

So thinking of the feature first, if it necessary or not.
(if it is) Then UI.
Comment 7 ace_dent 2008-05-17 21:18:49 UTC
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
Comment 8 ace_dent 2008-05-17 23:21:55 UTC
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Comment 9 cfynn 2011-04-06 05:23:03 UTC
Related to Bug 43207