Download it now!
Bug 127491 - Enter a half-width character at begining of line , The Language change from Japanese to English.
Summary: Enter a half-width character at begining of line , The Language change from J...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.3.1.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevAdvice, needsUXEval
Depends on:
Blocks: CJK CJK-Japanese
  Show dependency treegraph
 
Reported: 2019-09-11 07:26 UTC by nogajun
Modified: 2020-08-24 03:49 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
odt file (8.23 KB, application/vnd.oasis.opendocument.text)
2019-09-11 07:27 UTC, nogajun
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nogajun 2019-09-11 07:26:01 UTC
Description:
Enter a half-width character(or Inserted Tab) at begining of line, The Language change from Japanese to English.

Steps to Reproduce:
Option -> Languages Settings -> Languages

- Language Of
    - User interface: Default - Japanese
    - Locale setting: Japanese

- Default Languages for Ducuments
    - Western: Default - English (USA)
    - Asian: Default - Japanese

1. Start up a Writer
2. Confirm Text Language is "日本語" (Japanese) on Status bar.
3. Select menu: Insert -> Field -> Date when inserted "9月11日" (That's Good!)  

4. Enter a half-width character (ex. a, b or alphabetical character) at begining of line.
5. Status bar Text Language changes to "英語(米国)" (English (USA)).
6. Select menu: Insert -> Field -> Date when inserted "09/11/19" (That's Bad)


Actual Results:
Text Language changes to "English(USA)"

Expected Results:
Text Language is unchanged. Still "Japanese".


Reproducible: Always


User Profile Reset: Yes



Additional Info:
バージョン: 6.3.1.2
Build ID: b79626edf0065ac373bd1df5c28bd630b4424273
CPU threads: 4; OS:Linux 5.2; UI render: default; VCL: gtk3; 
ロケール: ja-JP (ja_JP.UTF-8); UI-Language: ja-JP
Calc: threaded
Comment 1 nogajun 2019-09-11 07:27:13 UTC
Created attachment 154095 [details]
odt file
Comment 2 Naruhiko Ogasawara 2019-11-17 03:12:15 UTC
Confirmed with:

Version: 6.3.3.2.0+
Build ID: libreoffice-6.3.3.2-snap1
CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3; 
Locale: ja-JP (ja_JP.UTF-8); UI-Language: en-US
Calc: threaded

But I'm not sure if this behavior is a bug or specification.

Even if the default paragraph language setting is Japanese, the paragraph language will be English when I enter English as the first character. Then I enter Japanese, the entire paragraph language will be Japanese.

However, the language shown in the status bar seems to be indicated "for selection," not a "for paragraph," and I guess it is correct that the "for selection" language changes depending on whether the characters are Japanese or English.
Comment 3 Franklin Weng 2019-11-21 05:36:23 UTC
(In reply to Naruhiko Ogasawara from comment #2)
> Confirmed with:
> 
> Version: 6.3.3.2.0+
> Build ID: libreoffice-6.3.3.2-snap1
> CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3; 
> Locale: ja-JP (ja_JP.UTF-8); UI-Language: en-US
> Calc: threaded
> 
> But I'm not sure if this behavior is a bug or specification.
> 
> Even if the default paragraph language setting is Japanese, the paragraph
> language will be English when I enter English as the first character. Then I
> enter Japanese, the entire paragraph language will be Japanese.
> 
> However, the language shown in the status bar seems to be indicated "for
> selection," not a "for paragraph," and I guess it is correct that the "for
> selection" language changes depending on whether the characters are Japanese
> or English.

Looking in more detail, when I type single quote ' the language in the status changed from Chinese(Taiwan) to English, but when I input Chinese character it jumped back to Chinese (Taiwan).  It looks like showing the (detected) language of current character (selections).

And the language settings and detecting seem to be for spellchecking, which would be usually useless in CJK, but would easily confuse users.

@Heiko, do you think it a UX problem to discuss?  Putting keyword first.
Comment 4 Heiko Tietze 2019-11-21 14:50:06 UTC
With tools > options > language you set the default for new documents [1] but the paragraph style [2] is relevant too. Not sure what the Default is for you.
And as far as I know, the language is bound to the font meaning a non-latin character switches it to English. It makes perfect sense for RTL vs. LTR: if you write some Arabic or Hebrew text from right to left including sections in English you want this part to be left to right. And the status bar reflects this. 
Correct, Regina?

There was a related request in bug 127897.

[1] https://help.libreoffice.org/6.3/en-US/text/shared/optionen/01140000.html
[2] https://help.libreoffice.org/6.3/en-US/text/shared/guide/language_select.html
Comment 5 Heiko Tietze 2019-12-13 08:17:54 UTC
Waiting for response from Regina. My take: WFM.
Comment 6 QA Administrators 2020-07-24 03:46:40 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2020-08-24 03:49:52 UTC
Dear nogajun,

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-FollowUp