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)
Text Language changes to "English(USA)"
Text Language is unchanged. Still "Japanese".
User Profile Reset: Yes
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
Created attachment 154095 [details]
Build ID: libreoffice-126.96.36.199-snap1
CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3;
Locale: ja-JP (ja_JP.UTF-8); UI-Language: en-US
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.
(In reply to Naruhiko Ogasawara from comment #2)
> Confirmed with:
> Version: 188.8.131.52.0+
> Build ID: libreoffice-184.108.40.206-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.
With tools > options > language you set the default for new documents  but the paragraph style  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.
There was a related request in bug 127897.
Waiting for response from Regina. My take: WFM.
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 INSUFFICIENTDATA
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!