Bug 166104 - All apostrophes change to Asian font when there is Asian text in the paragraph
Summary: All apostrophes change to Asian font when there is Asian text in the paragraph
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
25.2.0.1 rc
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, possibleRegression
Depends on:
Blocks:
 
Reported: 2025-04-09 14:57 UTC by psaubro
Modified: 2025-04-11 14:59 UTC (History)
1 user (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 psaubro 2025-04-09 14:57:15 UTC
Description:
When I mix roman alphabet-based language (French in my case) and Asian language (Japanese in my case) in the same paragraph, LibreOffice automatically changes all apostrophes in the paragraph to the font of the Asian text (MS Mincho in my case). This is annoying because Asian font apostrophes create a big blank. It is possible to change the font back to Liberation Serif, but you have to do it character by character.

Steps to Reproduce:
1. Write text with an apostrophe somewhere
2. In the same paragraph, add Japanese text
3. Press Enter

Actual Results:
All apostrophes in the paragraph turn to MS Mincho

Expected Results:
Apostrophes shouldn't automatically change font


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 25.2.2.2 (X86_64) / LibreOffice Community
Build ID: 7370d4be9e3cf6031a51beef54ff3bda878e3fac
CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: threaded
Comment 1 psaubro 2025-04-10 12:27:30 UTC
I should add that I've been using LibreOffice and mixing languages for years, but this bug has only started happening a month or two ago. I don't remember changing any of the settings of LibreOffice when it started; I think it was due to a software update.
Comment 2 meagan.eggert 2025-04-10 16:33:10 UTC
Version 25.2.1.2
Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49
CPU threads: 8; OS: Windows 11 x86_64
UI render: Skia/Raster; VCL: win
Locale: en-US; UI: en-US
Calc: threaded

Confirmed. I typed a paragraph in English, pasted in Japanese text, hit enter, and the apostrophes in the paragraph changed and spaced out.
Comment 3 psaubro 2025-04-11 10:56:36 UTC
Sorry for the multiple posts.
I went back to version 24.8.6.2 and can confirm the bug doesn't happen in this version of LibreOffice.
I think this is due to the fix for bug #66791 (https://bugs.documentfoundation.org/show_bug.cgi?id=66791), which has been implemented in version 25.2.
Comment 4 Ming Hua 2025-04-11 12:07:11 UTC
(In reply to psaubro from comment #3)
> I went back to version 24.8.6.2 and can confirm the bug doesn't happen in
> this version of LibreOffice.
> I think this is due to the fix for bug #66791
> (https://bugs.documentfoundation.org/show_bug.cgi?id=66791), which has been
> implemented in version 25.2.
Quite possible.

Jonathan, would you please have a look at this?
Comment 5 Saburo 2025-04-11 14:05:24 UTC
bisected
commit 73a96633d672f344f6415f050405b19174031f37
author	Jonathan Clark <jonathan@libreoffice.org>	Tue Dec 10 02:25:31 2024 -0700

tdf#66791 sw: Treat weak punctuation as Asian in Asian paragraphs

This change modifies script detection to treat certain weak punctuation
marks, particularly left- and right- quotation marks, as Asian script in
paragraphs containing Chinese and Japanese characters, but no Complex
characters. This change improves our script detection compatibility with
other programs.

As part of this change, duplicated script detection code has been
extracted from Writer and Edit Engine, and consolidated.

***
As stated in comment 3.

If you set the Western Languages ​​font to MS Mincho, single quotes will become full-width while you type.

This does not work unless you uncheck Replace single quotes in the localized options of AutoCorrect options.
Comment 6 Volga 2025-04-11 14:58:17 UTC Comment hidden (no-value)
Comment 7 Volga 2025-04-11 14:59:37 UTC
I've already seen that.

https://bugs.documentfoundation.org/show_bug.cgi?id=66791#c41