View Issue Details

IDProjectCategoryView StatusLast Update
0015541ScribusFontspublic2022-01-16 13:44
ReporterGibbz Assigned Tojghali  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version1.5.4 
Summary0015541: Japanese characters dont work well
DescriptionI need to convert one of my flyers to have Japanese characters. But have found scribus just displays red boxes for the characters.
It looks like its not mapping the character codes to their glyph's.

In the story editor they show up fine, just not in the document.

For now my workaround is to use Arial Unicode MS.
Steps To Reproducehttp://generator.lorem-ipsum.info/_japanese
copy some japanese
paste into scrubs
Additional InformationRunning on windows 10.
TagsNo tags attached.
PatchNo

Relationships

has duplicate 0016722 closedjghali Story Editor loses properly displayed Japanese characters on save 

Activities

jghali

2019-01-18 00:06

administrator   ~0045805

Last edited: 2019-01-18 00:11

Not all fonts are suitable to perform Japanese text layout. The font has to contains the proper glyphs for Japanese characters. Arial Unicode MS is one of those fonts which can handle Japanese characters while the standard Arial does not. Lots of office applications are performing font substitutions when a user tries to use characters which do not exist in current font. This is not the case for Scribus... and this is intended.

The story editor display font is not linked to the fonts used on canvas as the main purpose of story editor is to type text. Font and text handling is simplified in text editor in order to make it more efficient for long text editing. The story editor will generally use a single display font which can be changed using Settings > Display font... and may perform font substitution if some characters are not available in current display font.

Issue History

Date Modified Username Field Change
2019-01-17 22:47 Gibbz New Issue
2019-01-18 00:06 jghali Assigned To => jghali
2019-01-18 00:06 jghali Status new => resolved
2019-01-18 00:06 jghali Resolution open => no change required
2019-01-18 00:06 jghali Note Added: 0045805
2019-01-18 00:11 jghali Note Edited: 0045805
2019-01-18 00:16 jghali Sticky Issue No => Yes
2019-01-18 00:16 jghali Sticky Issue Yes => No
2019-01-18 13:03 jghali Status resolved => closed
2022-01-16 13:44 jghali Relationship added has duplicate 0016722