View Issue Details

IDProjectCategoryView StatusLast Update
0013644ScribusQt5 Portpublic2016-03-07 13:46
ReporterJLuc Assigned To 
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status newResolutionopen 
PlatformLinuxOSUbuntuOS Version14.04
Product Version1.5.1 
Summary0013644: More than 4 hexigits unicodes
DescriptionScribus "insert character" glyph table dialog only enables 4 hexigits unicode inputs.

Decimal 128198 unicode glyph or hex 📆 can't be typed in because it's 5 hexigits (hexadecimal digit). (About this glyph : (http://www.fileformat.info/info/unicode/char/1f4c6/index.htm )

Could the insert glyph input dialog be extended so as to allow 5 or 6 hexigits unicodes ?
Tagsupstream
PatchNo

Activities

jghali

2016-01-11 17:38

administrator   ~0038070

Last edited: 2016-01-11 17:40

Currently Scribus text layout supports only 16bit encoded unicode values. So adding 5 or 6 hexigits unicodes to Insert > Glyph is not possible at this point.

Kunda

2016-01-12 15:48

updater   ~0038083

jghali, add this to a 'Future Release's ?

jghali

2016-01-12 16:08

administrator   ~0038085

Last edited: 2016-01-12 16:11

No, this feature does not depends only on us. Qt needs first to support unicode range above 65535, which is something we will not see in Qt 5. Until then, that feature cannot be seen as part of a future release.

Kunda

2016-01-12 16:34

updater   ~0038086

jluc, if you find the Qt upstream feature request you can link it to this ticket and we can tag this 'upstream'

JLuc

2016-01-12 19:57

developer   ~0038089

I created a qt report : https://bugreports.qt.io/browse/QTBUG-50430

JLuc

2016-01-13 12:19

developer   ~0038109

Answer on Qt bug tracker says : "Qt supports the whole range of Unicode code points. see QString::fromUcs4()"

Its documented here : http://doc.qt.io/qt-5/qstring.html#fromUcs4

jghali

2016-01-13 12:49

administrator   ~0038110

Last edited: 2016-01-13 12:49

QChar doesn't allow storing unicode values above 65535.

jghali

2016-01-13 12:51

administrator   ~0038111

Anyway your bug was at most a duplicate of https://bugreports.qt.io/browse/QTBUG-18868

JLuc

2016-01-19 19:27

developer   ~0038290

Last edited: 2016-01-19 19:27

Question : How should unicodes with more than 2 hexigits be managed when QString indices are actually 16-bit indices ?

Qt dev answers : qDebug() << QString::fromUcs4(&ucs4, 1);

Issue History

Date Modified Username Field Change
2016-01-11 15:30 JLuc New Issue
2016-01-11 16:28 JLuc Description Updated
2016-01-11 16:29 JLuc Description Updated
2016-01-11 17:38 jghali Note Added: 0038070
2016-01-11 17:38 jghali Severity minor => feature
2016-01-11 17:40 jghali Note Edited: 0038070
2016-01-12 15:48 Kunda Note Added: 0038083
2016-01-12 16:08 jghali Note Added: 0038085
2016-01-12 16:11 jghali Note Edited: 0038085
2016-01-12 16:34 Kunda Note Added: 0038086
2016-01-12 19:57 JLuc Note Added: 0038089
2016-01-13 01:14 Kunda Tag Attached: upstream
2016-01-13 12:19 JLuc Note Added: 0038109
2016-01-13 12:49 jghali Note Added: 0038110
2016-01-13 12:49 jghali Note Edited: 0038110
2016-01-13 12:51 jghali Note Added: 0038111
2016-01-19 19:27 JLuc Note Added: 0038290
2016-01-19 19:27 JLuc Note Edited: 0038290
2016-03-07 13:46 Kunda Category User Interface => Qt5 Port