It is not possible to type into Writer any *supplementary plane* chars mapped to the AltGr state. These chars simply do not appear on screen, on export, or on printing. By contrast, AltGr-mapped *BMP* chars are OK, as are *supplementary plane* chars mapped to normal or shift states. There is also no problem typing AltGr-mapped *supplementary plane* chars into Calc & Impress. These chars can also be readily produced with AltGr in other apps like Word & Excel.
This problem is attested in the following builds & OS:
- LibO 220.127.116.11 on 64-bit English Windows 7 Ultimate SP1
- LibO 18.104.22.168 on 64-bit English Windows 7 Ultimate SP1
Steps to reproduce bug:
1. download & install Miao Unicode font at https://github.com/phjamr/MiaoUnicode/blob/master/MiaoUnicode-Regular.ttf?raw=true
2. unzip attached archive & install Ahmao keyboard (run setup.exe)
3. run Writer & set all Basic Fonts (CTL) to Miao Unicode (in Tools|Options|LibreOffice Writer)
4. select Miao Unicode font
5. on Windows language bar, select MR
6. refer to the 3 .jpg files in attached archive for keys mapped in each state
7. type any mapped keys in normal state: Miao chars (mostly big letters) appear in document -- expected
8. type any mapped keys in shift state: Miao chars (mostly small letters) appear in document -- expected
9. type any mapped keys in AltGr state: *nothing appears* -- BUG!!!
10. select 'Export to pdf' or 'Print' from the File menu: no sign of any chars typed in #9 -- BUG!!!
Control experiments with other apps:
11. open Calc/Impress/Word/Excel/PowerPoint: blank document appears
12. repeat #4-8: expected results
13. type any mapped keys in AltGr state: Miao chars (big letters with wart) appear in document -- expected
Further observations: Writer may be cutting off the 2nd half of the surrogate pair that represents a supplementary char, as suggested by the following test:
14. in Writer, repeat #7-8 in any order multiple times, keeping all chars on 1 line
15. repeat #9 multiple times, continuing on the same line as in #14
16. copy the whole line & paste into Word: a line of blanks appears with trailing 'checked' boxes
17. in Word, place cursor after any 'checked' boxes
18. press Ctrl-X: the string D81B appears, which is the Unicode code point of the 1st half of any surrogate pair representing chars in this (Miao) block
Further control experiment with BMP chars (Hebrew):
19. download & install SBL Hebrew font at http://www.sbl-site.org/Fonts/SBL_Hbrw.ttf
20. download & install SBL Hebrew Tiro keyboard at http://www.sbl-site.org/Fonts/BiblicalHebrewTiro.zip
21. download & refer to SBL Hebrew Tiro keyboard layout at http://www.sbl-site.org/Fonts/BiblicalHebrewTiroManual.pdf
22. in Writer, select SBL Hebrew font
23. on Windows language bar, select HE
24. type any mapped keys in any state: Hebrew chars appear as expected
Created attachment 87837 [details]
Ahmao Unicode keyboard + layout
BTW, the Miao script is used by multiple language groups with as many as 6 million people. It would be most appreciated if you could fix this ASAP. Thank you!
This bug is also attested in the following LibO versions, all on 64-bit English Windows 7 Ultimate SP1:
Symptoms (in step 9) are not exactly the same but similar in nature:
LibO 22.214.171.124: a square appears & then changes to crossed boxes on typing further chars mapped to AltGr
LibO 126.96.36.199: nothing appears
LibO 188.8.131.52: similar to 184.108.40.206 plus random line splitting or glyph change on screen which will revert to original on further typing
- if a char mapped to AltGr starts the line, a square appears & subsequent consecutive AltGr-mapped chars on the same line are not rendered at all
- otherwise, chars mapped to AltGr are rendered as crossed boxes
- these symbols (square/crossed box/nothing) will randomly switch among themselves so that sometimes part of the line just disappears & comes back again on typing further chars
Version field set to 3.3.1 release to reflect earliest occurrence attested.
Another case of Writer 220.127.116.11 blocking output of SMP chars mapped to AltGr & shift-AltGr states:
Steps to reproduce bug with Tengwar (re-encoded at U+1CC00..1CC7F for testing):
1. unzip tengmod.zip attached
2. install Tengwar font (right-click tengmod.ttf & select Install)
3. install Tengwar keyboard (run setup.exe)
4. run Writer
5. select Tengwar Telcontar Mod font
6. on Windows language bar, select IS
7. refer to the 4 .jpg files in attached archive for keys mapped in each state
8. type any mapped keys in AltGr or shift-AltGr state: squares & nothing appear -- BUG!!!
According to dev comments re a parallel bug in AOO, this appears to be caused by processing Unicode codepoints via the operator ::rtl::OUString::operator sal_Unicode*, which is defined as only 16-bit unsigned int, effectively dropping all codepoints beyond BMP (thus the surrogate pair cut-off phenomenon). Pls. kindly revise the code base in concern to use a 32-bit type & fix this defect ASAP.
Created attachment 94751 [details]
Tengwar test font, keyboard, & layout
Attested also in Writer 18.104.22.168 for both Miao & Tengwar.
Enhancement request as per comment 4. Please also add the mentioned bug in 'see also:'
The parallel bug for OO has no comments.
Also, the proper keyboard handling is anything but enhancement.
Added link to parallel OO bug #124312. Note that OO dev added a link in the 'Blocks' field to the possible root cause (per comment #4). That 2nd link is also included in the 'See Also' field here. For the sake of the several million Miao script users, pls. kindly look into this issue at your earliest convenience. Thanks!
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.
For more information about our NEEDINFO policy please read the wiki located here:
If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):
a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue.
Please do not:
a) respond via email
b) update the version field in the bug or any of the other details on the top section of FDO
We already provided the requested info 8.5 months ago (see comment 9 added on 2014-03-06 18:12:51 UTC, 24 mins. after comment 8 & 78 mins after comment 7). We don't know what more info you need. Pls. specify.
We just tested with the latest release 22.214.171.124 on 32-bit English Windows Vista Business & the bug is still there:
- No chars in the AltGR & shift-AltGR states can be produced.
- For Ahmao, nothing appeared at all (rf. Description, step #9).
- For Tengwar, spaces appeared instead (cf. Comment 4, step #8).
- When the 'empty' string is copied into Word 2003 & Alt-X pressed,
- D81B appeared for Ahmao (rf. Description, step #18; NB: 'Ctrl-X' should read 'Alt-X').
- D833 appeared for Tengwar.
Apparently the surrogate cut-off problem is still not resolved. Pls. kindly fix it asap. Thanks!
It's been a year already but nothing has happened apart from defect confirmation. Pls. kindly follow up asap. Thanks!
With a current build of LO master/5.3.0alpha0+ (Build ID: 696e83b663d4f3e00f23947613f9f3916a4dd14d) on install of Miao unicode font linked in comment 0 -- the Special Character dialog displays and selects glyphs and allows paste of SMP codepoints into the Writer canvas. The <alt>+X unicode toggle also seems to work correctly for the SMP codepoints.
Could you check if your preferred AltGr based text IME remains balky in Writer for entering SMP codepoints for the font.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice
(5.4.1 or 5.3.6 https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
This issue was confirmed to be resolved in the following build & OS:
- Version 126.96.36.199 (x64) on 64-bit English Windows 7 Ultimate SP1
*HOWEVER*, it is still attested in the following NEWER builds & OS:
- Version 188.8.131.52 (x64) on 64-bit English Windows 7 Ultimate SP1
- Version 184.108.40.206 (x64) on 64-bit English Windows 10 Pro
- Version 220.127.116.11 (x64) on 64-bit English Windows 10 Pro
A minor difference is instead of squares, black diamonds with a white question mark inside are produced. On pressing Alt-X, the same surrogate values show up as before.
This indicates other fixes in the code base for 6.x has broken the fix for this issue in 5.4 => regression!
Created attachment 151415 [details]
picking SMP glyphs via Special Character dialog
(In reply to nrs from comment #16)
On Windows 10 Ent 64-bit en-US (1807) with
Version: 18.104.22.168 (x64)
Build ID: 170a9c04e0ad25cd937fc7a913bb06bf8c75c11d
CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win;
Locale: en-US (en_US); UI-Language: en-US
Can not confirm mishandling of SMP Unicode glyphs. The IME may be wrong, but handling to document canvas with Special Character dialog, or <Alt>+X toggle correctly assigns the SMP Unicode glyphs.
Thank you for your quick response! I can also get the desired char via the Special Char dialog, but pls. kindly reread comment #1: This issue is about *typing*, not about pointing & clicking. And the various control experiments with other apps, including Calc, clearly confirm that the keyboards are working.
The only conclusion possible is that:
- either something in the Writer 6.x code base broke the fix that was in place in 5.4, or
- the fix available in 5.4 is not incorporated into Writer 6.x at all.
Pls. kindly double-check. Thanks!