Bug 74735 - FORMATTING: Smart quotes mismatch when using English and Asian languages interexchangebly
Summary: FORMATTING: Smart quotes mismatch when using English and Asian languages inte...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoCorrect-Complete
  Show dependency treegraph
 
Reported: 2014-02-09 07:18 UTC by LL
Modified: 2023-08-30 03:06 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description LL 2014-02-09 07:18:57 UTC
When Smart Quote is turned on, the closing quote of a quote enclosing an Asian phrase uses the Asian font face and Asian quote, while the opening quote uses Western font face and Western quote.

I.e., it may become >> Land Management Law of the PRC (“中华人民共和国土地管理法』)
or >> Land Management Law of the PRC (“中华人民共和国土地管理法”) [*where the '”' is in a different font face from the '“']

The closing quote *always* retains its default automated form even if it is manually replaced, unless the Smart Quote function is switched off.
Comment 1 Mihkel Tõnnov 2014-02-11 20:26:54 UTC
Confirming that the closing quote mark is in different font (Code2000 in my case) than the opening one (Liberation Serif) -- couldn't get it to look like a Chinese quote mark, though.
Tried on Linux (with LibO 4.2.0 RC4), so probably affects all platforms.
Comment 2 Joel Madero 2015-05-02 15:41:06 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2016-09-20 09:36:56 UTC Comment hidden (obsolete)
Comment 4 Thomas Lendo 2019-08-29 23:17:07 UTC
Still reproducible with Version: 6.3.0.4
Build ID: 057fc023c990d676a43019934386b85b21a9ee99
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: de-AT (de_AT.UTF-8); UI-Language: en-US
Comment 5 QA Administrators 2021-08-29 04:08:53 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2023-08-30 03:06:02 UTC
Dear LL,

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 with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

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) from https://downloadarchive.documentfoundation.org/libreoffice/old/

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: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug