Issue 23716 - [Inconsistency] Hide non-printable fonts from Insert-Special Charcter
Summary: [Inconsistency] Hide non-printable fonts from Insert-Special Charcter
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC5
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2003-12-19 13:05 UTC by ulf.stroehler
Modified: 2017-05-20 11:19 UTC (History)
2 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description ulf.stroehler 2003-12-19 13:05:32 UTC
In general OOo offers font types (printable/non-printable ones) depending on the
purpose of the apllication.

That means applications with a typically use case to print documents only
provide printable fonts. This prevents user error and invalid issue reports (of

* example is the Writer.

Applications with a typical use case of generating online documents, are less
strict and provide *ALL* available fonts.

* example is Impress or HTML-Writer resp. Writer in Online Layout. Infact
switching the Writer from document view to Online Layout changes the amount of
available fonts.

Unfortunately the Insert/Special Character dialog doesn't care about the
application or the document view (Online Layout on/off).
It always provides *All* fonts.
This is problematic as users may for example choose mathematical symbols from
Insert/Special Character, which do not appear in the print-out later on (WAS
issue 17731).

The enhancement:
the "Insert/Special Charactr" dialog should display fonts in accordance to the
application from which it was called like the "Format/Character" dialog does.
Comment 1 bettina.haberer 2004-01-20 17:35:29 UTC
Summary: The "Insert/Special Character" dialog should display fonts in
accordance to the application from which it was called like the
"Format/Character" dialog does.
Hello Herbert, please give approval for this evaluated OO.o 2.0 flagged issue. 
If you confirm with the target OO.o 2.0, then please keep it on your owner (or
the owner of the concerning developer) for implementation. In case you want this
issue for 'OOo Later', then please reset the target milestone. If you decline
the issue finally, please set the resolution to 'Wontfix' (but do not close). In
case of 'OOo Later' or 'Wontfix' please reset it on Bettina's owner. Thank you.
Comment 2 2004-01-21 08:45:01 UTC
Comment 3 ulf.stroehler 2004-05-25 14:58:11 UTC
According to the OOo roadmap retargeting to 'OOo Later'.
Comment 4 ulf.stroehler 2004-05-25 15:00:49 UTC
Changing owner to bh as requested.
Comment 5 bettina.haberer 2004-05-25 15:51:49 UTC
As the developer has accepted the issue, it does not make sense to reassign it
to me. Reassigning on "OO.o later" to me is ok, if development has not accepted
an issue. So this one is set back to development.
Comment 6 bettina.haberer 2004-05-25 15:54:53 UTC
Reassigned to Herbert.
Comment 7 bettina.haberer 2004-05-25 15:56:48 UTC
Reset from new to started, as it already was accepted by development.
Comment 8 Marcus 2017-05-20 11:19:39 UTC
Reset assigne to the default "".