Closed Bug 188296 Opened 23 years ago Closed 5 years ago

Can't specify non-western fonts in composer

Categories

(Core :: Internationalization, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: xslf, Assigned: smontagu)

References

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.3b) Gecko/20030101 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.3b) Gecko/20030101 Composer lets you specify fonts in your HTML. However, it will only let you select from a pre-defined list, which contains only western fonts- not suitble for Hebrew pages. Reproducible: Always Steps to Reproduce: 1. Create a new document in composer, encoding windows-1255 2. Format- font and attempt to select a specific font Actual Results: Only western fonts are avalible Expected Results: there should be a way to specify custom fonts, that are suitble for the encoding used
Blocks: 152111
This fits better in "Internationalization" than in "Layout: Bidi".
Assignee: mozilla → smontagu
Component: Layout: BiDi Hebrew & Arabic → Internationalization
QA Contact: zach → amyy
On my system, that menu shows all fonts installed on my system AFAICT (including e.g. Arabic and CJK fonts), BUT I have userChrome.css rules to add scrollbars to long menus (and suppress arrowscrollboxes if any), see here at bottom. So: - is this Mac-only? (Sounds strange to me) - was it fixed in another bug by adding arrowscrollboxes at top and bottom of long menus (similar to bug 245163 but for menubar menus)? Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008031601 SeaMonkey/2.0a1pre /* * give the menus a scrollbar when they are too high to be * displayed in full */ menupopup scrollbox, #contentAreaContextMenu scrollbox { overflow-y: auto !important } /* * eliminate scroll buttons at top and bottom of the menus */ menupopup autorepeatbutton, #contentAreaContextMenu autorepeatbutton { display: none !important }
QA Contact: amyy → i18n
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.