Created attachment 138729 [details] The screenshot of the Font tab of the "Title" style in the first slide of the Progress template Tested in Daily build (2017-12-28_10.01.02) and Chinese (traditional) locale (zh-tw). The default templates of Impress provide poor default Asian fonts settings. Let's take the "Progress" template for example. How reproducible: always Reproduce Steps: 1. Install Daily Build and set the locale to Chinese (traditional) in Tools > Options > Language Settings > Language > Language Of "Locale setting" to "Chinese (traditional)" and enable Default Languages for Documents "Asain:" checkbox then seclect "Chinese (traditional)" 2. Press OK and restart 3. Open Impress and select any of the default templates, such as "Progress" for example here. Actual Result of the styles in the first slide of the Progress template: In the Font tab of the "Title" style: Western Text Font Family: Liberation Sans Style: Bold Size: 75 Asian Text Font Family: 思源宋體 Style: Regular Size: 24 In the Font tab of the "Outline 1" style: Western Text Font Family: Liberation Sans Style: Regular Size: 36 Asian Text Font Family: 思源宋體 Style: Regular Size: 24 Expected result: 1. Sans-serif font families should mapped to any 黑體/方體/ゴシック (Hei/Fung/Gothic typeface). In the case of zh-tw locale, it should map to the CJK_HEADING of zh-tw locale defined in VCL.xcu. 2. Serif font families should map to any 明體/宋體/明朝體 (Ming/Sung/Mincho typeface). In the case of zh-tw locale, it should map to the CJK_TEXT of zh-tw locale defined in VCL.xcu. 3. The Asian Text Font "Style" and "Size" should be in coherent with Western Text Font Style and Size. If it is Bold and 75 points for Western Text, it is better to be the same for Asian Text. Bottom line: Mostly all the templates have the problems on Asian Text Font Family, Style and Size. It is best to have a corresponding setting for each locale. If that cannot be done, just use the same generic font family (matchmaking for Sans and Serif fonts), the same style (Regular, Bold, etc.), and the same size. PS. here is a brief view of the first candidate CJK font of zh-tw locale in VCL.xcu: CJK_HEADING: 思源黑體 (Source Han Sans) CJK_TEXT: 思源宋體 (Source Han Serif) CJK_PRESENTATION: 思源黑體 (Source Han Sans) CJK_SPREADSHEET: 思源黑體 (Source Han Sans)
(In reply to Cheng-Chia Tseng from comment #0) > 1. Sans-serif font families should mapped to any 黑體/方體/ゴシック (Hei/Fung/Gothic > typeface). In the case of zh-tw locale, it should map to the CJK_HEADING of > zh-tw locale defined in VCL.xcu. > 2. Serif font families should map to any 明體/宋體/明朝體 (Ming/Sung/Mincho > typeface). In the case of zh-tw locale, it should map to the CJK_TEXT of > zh-tw locale defined in VCL.xcu. All the impress templates use sans-serif fonts, so as no setting is defined in the template files, it should automatically pull the correct font based on VCL.xcu from CJK_PRESENTATION. But if a serif font is defined, i dont think there is a odf attribute that could be set that would cause LO to choose the correct font from VCL.xcu. Maxim, Regina: thoughts? > 3. The Asian Text Font "Style" and "Size" should be in coherent with Western > Text Font Style and Size. If it is Bold and 75 points for Western Text, it > is better to be the same for Asian Text. As the cjk and ctl font size and weight isnt defined in the tag, i would have expected that it would utilize the same settings used in latin, so this likely can be fixed in code, or alternatively we could add style:font-size-asian, style:font-weight-asian, style:font-size-complex, and style:font-weight-complex attributes.
>All the impress templates use sans-serif fonts, so as no setting is defined in the template files, it should automatically pull the correct font based on VCL.xcu from CJK_PRESENTATION. But if a serif font is defined, i dont think there is a odf attribute that could be set that would cause LO to choose the correct font from VCL.xcu. Actually, I found the "Vintage" template of Impress using Liberation Serif. BTW, many templates shipped in other office suites (such as MS Office and Apple Keynote) also use Serif in some Impress templates. So we still have to take Serif into consideration.
"Progress" and some other Impress templates have been updated in 6.0.0 RC2 See https://bugs.documentfoundation.org/show_bug.cgi?id=103317#c26 Please check if sizes of Asian fonts are now correct.
(In reply to Laurent BP from comment #3) > "Progress" and some other Impress templates have been updated in 6.0.0 RC2 > See https://bugs.documentfoundation.org/show_bug.cgi?id=103317#c26 > > Please check if sizes of Asian fonts are now correct. This is tested in Daily build (2017-12-28_10.01.02). Not resolved yet.
(In reply to Yousuf Philips (jay) from comment #1) > As the cjk and ctl font size and weight isnt defined in the tag, i would > have expected that it would utilize the same settings used in latin, so this > likely can be fixed in code, or alternatively we could add > style:font-size-asian, style:font-weight-asian, style:font-size-complex, and > style:font-weight-complex attributes. Actually I removed all these tags, because I was expecting such behavior: use latin settings for size and weight with asian and complex. This may be a different bug report.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Same as previous status on 6.4.0.0.alpha0+. (master~2019-09-28_15.31.38) Verision: バージョン: 6.4.0.0.alpha0+ Build ID: 66e45a1ae861d50edf65fed9e39c9c9d5b15e0ac CPU threads: 8; OS:Linux 5.2; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-09-28_15:31:38 ロケール: ja-JP (ja_JP.UTF-8); UI-Language: ja-JP Calc: threaded This is a critical bug for CJK users. Reproduce Steps: Select Progress theme from theme selector. then Title Fonts is - English(USA): Liberation Sans / Bold /75pt - Japanese: Noto Serif CJK JP / Normal / 24pt (Serif???) The correct fonts is Noto Sans CJK JP(Sans) / Bold / 75pt.
Reset Version to earliest affected
Laurent BP committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f7a584a592b0e481f974039288da585201c60747 tdf#114746 Restore asian and complex tags in Progress template It will be available in 6.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Laurent BP committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/457be5006ea029e872a04d1c4e55b450863804a0 tdf#114746 Restore asian and complex tags in Alizarin template It will be available in 6.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Laurent BP committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/b1fdf58b607be68089a142cbaa476b86e4a632a1 tdf#114746 Restore asian and complex tags in Beehive template It will be available in 6.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Laurent BP committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/7b13f1efa835a90fd1c5554b70a62bf8e395a69f tdf#114746 Restore asian and complex tags in Blue_Curve template It will be available in 6.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Laurent BP committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f8ad76e1ea0ba0bacce75f98f4f60dbb86c284a6 tdf#114746 Restore asian and complex tags in Blueprint_Plans template It will be available in 6.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Laurent BP committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/d69bc15a2a76ccecbed64984972417c7fe0a475b tdf#114746 Restore asian and complex tags in BrightBlue template It will be available in 6.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Laurent BP committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e0f06e60c6e8958bc508d24585189043888e0eb9 tdf#114746 Restore asian and complex tags in Classy_Red template It will be available in 6.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Can somebody using Asian or complex UI test in LibO 6.4.0RC1 if Progress template has now better rendering with correct font sizes? If it works for Progress template, I will extend this patch to other templates.
Env: Version: 6.4.0.1 Build ID: 1b6477b31f0334bd8620a96f0aeeb449b587be9f CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: th-TH (zh_TW.UTF-8); UI-Language: en-US Calc: threaded Reproduce Steps: (1) Change the local setting. (2) Select the theme "Progress" from theme selector. (3) Open the font setting dialog for "Title". Result: ---------------------------------------------- If Local Setting is English (USA) Western Text Font: Libration Sans, Bold, 75pt Asian Text Font: DejaVu Sans, Bold, 75pt Complex Text Font: Noto Sans CJK TC, Bold, 75pt ---------------------------------------------- If Local Setting is Chinese (Trad) Western Text Font: Libration Sans, Bold, 75pt Asian Text Font: Noto Serif CJK TC, Bold, 75pt Complex Text Font: Noto Sans CJK TC, Bold, 75pt ---------------------------------------------- If Local Setting is Japanese Western Text Font: Libration Sans, Bold, 75pt Asian Text Font: Noto Serif CJK JP, Bold, 75pt Complex Text Font: TakaoPGothic, Bold, 75pt ---------------------------------------------- If Local Setting is Korean (RoK) Western Text Font: Libration Sans, Bold, 75pt Asian Text Font: Noto Serif CJK KR, Bold, 75pt Complex Text Font: Noto Sans CJK TC, Bold, 75pt ---------------------------------------------- If Local Setting is Thai Western Text Font: Libration Sans, Bold, 75pt Asian Text Font: Waree, Bold, 75pt Complex Text Font: Kinnari, Bold, 75pt ---------------------------------------------- Issues: (1) Noto "Serif" CJK is used, which should be Noto "Sans" CJK. (2) Why a CJK font is used for CTL, when local is Western/CJK? (3) Regarding to Thai, "Kinnari" seems not a sans font?
@Hiunn-hé: thanks for your tests. Size, style and weight are now forced to be the same. These properties can be defined inside XML code of templates. Modifications of templates are on the way. Unfortunately, I don't know how to fix font changing for the issues you mentioned.
Laurent BP committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/fcf1e5b44429ce639cdd0f10def92a9d1822a0b1 tdf#114746 Restore asian and complex tags in templates It will be available in 6.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Laurent BP committed a patch related to this issue. It has been pushed to "libreoffice-6-4": https://git.libreoffice.org/core/commit/8c014938c523a4ee1bd8950781fe2a830b08cef1 tdf#114746 Restore asian and complex tags in Impress templates It will be available in 6.4.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Reproduce. it is not fixed. Version: 7.1.2.2 / LibreOffice Community Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4 CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: ja-JP (ja_JP.UTF-8); UI: ja-JP Calc: threaded
(In reply to Hiunn-hué from comment #17) > Issues: > (1) Noto "Serif" CJK is used, which should be Noto "Sans" CJK. CJK font fallback, it seems to refer to CJK_TEXT and not CJK_PRESENTATION in VCL.xcu. You can check this by following the steps below. 1. Open Options, Go to LibreOffice -> Advanced, Click "Open Expert Configuration". 2. Search for "CJK_TEXT". 3. Double-click on the Asian language you are using and add the SansSerif fonts to the top of the Value. 4. open the template from Impress Template.
Reported a bug about not referring to CJK_PERSENTATION. 142667 – Impress CJK font fallback refers to the wrong font list: https://bugs.documentfoundation.org/show_bug.cgi?id=142667
Jun Nogata committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/3adf0140c1c31ea82c023250f23404b6b54f833a tdf#114746 Fix CJK and CTL font style in Impress templates It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.