Bug 97309 - UI: Thai in Sheet name start with numbers and/or symbols shown as square
Summary: UI: Thai in Sheet name start with numbers and/or symbols shown as square
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.0.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-22 05:08 UTC by oakyman
Modified: 2016-11-08 12:59 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot (24.62 KB, image/png)
2016-01-22 05:08 UTC, oakyman
Details
ODS file contains the bug (7.61 KB, application/vnd.oasis.opendocument.spreadsheet)
2016-01-22 05:09 UTC, oakyman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description oakyman 2016-01-22 05:08:07 UTC
Created attachment 122137 [details]
Screenshot

When there are Thai characters in sheet name starts with number and/or symbols (such as -, _, ", ', \, +, =, all symbols in US keyboard) only, Thai characters are shown as square.
But if there are a-z, A-Z in sheet name, Thai characters are shown correctly.

OS: Windows 7 SP1 32-bit
Comment 1 oakyman 2016-01-22 05:09:37 UTC
Created attachment 122138 [details]
ODS file contains the bug
Comment 2 oakyman 2016-01-22 05:23:59 UTC
Workaround:
1) Open Options via Tools -> Options...
2) In LibreOffice -> Fonts
3) Check "Apply replacement table" checkbox
4) In "Replacement Table", enter the following values in the fields below 
  - Font: Segoe UI
  - Replace with: Tahoma
5) Click check mark button to add
6) Check "Always" and "Screen only" checkboxes
7) Click "OK" button

From https://groups.google.com/forum/embed/?place=forum/libreofficeclub&showsearch=true&showpopout=true&showtabs=false&hl=th&parenturl=http%3A%2F%2Fwww.libreofficeclub.com%2Fp%2Fask-libreoffice-club.html#!topic/libreofficeclub/OByqyxnzslU
Comment 3 Buovjaga 2016-01-28 15:15:54 UTC
No problem for me.

Win 7 Pro 64-bit, Version: 5.0.4.2 (x64)
Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78
Locale: fi-FI (fi_FI)

Version: 5.2.0.0.alpha0+
Build ID: 6b65a0e83c4798f117be61af91dbaebdc85e94b7
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-01-21_03:41:08
Locale: fi-FI (fi_FI)
Comment 4 Robinson Tryon (qubit) 2016-03-06 18:32:29 UTC
(In reply to oakyman from comment #2)
> Workaround:
> ...
> 4) In "Replacement Table", enter the following values in the fields below 
>   - Font: Segoe UI
>   - Replace with: Tahoma

What's the thinking here? Something to do with what glyphs are available in one Font family vs. another? (Looks like the libreofficeclub website is in thai)

(In reply to Beluga from comment #3)
> No problem for me.
> 
> Win 7 Pro 64-bit, Version: 5.0.4.2 (x64)
> ... 
> Version: 5.2.0.0.alpha0+

Always possible it's been fixed between 5.0.3 and now.
oakyman: Can you reproduce the problem in LO 5.0.5, 5.1.0, or (a daily build of) 5.2?
https://www.libreoffice.org/download/libreoffice-fresh/

Status -> NEEDINFO
Comment 5 Xisco Faulí 2016-10-10 11:25:01 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2016-11-08 12:59:28 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20161108