On 2023-07-03 12:59, Gunnar Hjalmarsson wrote:
> (But I notice another weird issue: In the FF Settings it shows Ubuntu
> as the default serif font irrespective of locale. How come?)
Pls disregard that. User error.
--
You received this bug notification because you are a member of Desktop
Sorry for late response. I filed bug #2025651.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/2017076
Title:
default Chinese font in snap apps is ugly
Status in Snappy:
On 2023-07-03 11:08, Sebastien Bacher wrote:
> Could you use a new bug to discuss the japanese issue?
Yes, Mitsuya plans to submit a new bug once he has checked mantic. (I
have used this one in the meantime to share a couple of thoughts.)
> It could help also to know if you are using the core20
Could you use a new bug to discuss the japanese issue?
It could help also to know if you are using the core20 or core22 version
of firefox and they have the same issue. Is the configuration in the
snap environment matching the real system one?
--
You received this bug notification because you
I think the reason why fonts-droid-fallback is installed by default is
this dependency chain:
ubuntu-desktop -> ghostscript-x -> ghostscript -> libgs10 ->
libgs10-common -> (recommends) fonts-droid-fallback
A fragile workaround might be to somehow stop fonts-droid-fallback from
being pulled
> I am concerned that it only affects the snap package, while
> the non-snap package seems to select the correct glyphs.
Yes, that's what it looks like.
$ lsb_release -c
No LSB modules are available.
Codename: mantic
$ dpkg-query -W fonts-droid-fallback
fonts-droid-fallback
** Attachment added: "lunar without fonts-droid-fallback"
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5683311/+files/Screenshot%20from%202023-07-02%2013-33-22.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
@Gunnar
Thanks for the advice. I removed fonts-droid-fallback and tried it, and
now Japanese glyphs are displayed.
However, I am concerned that it only affects the snap package, while the
non-snap package seems to select the correct glyphs.
I will first check if this also happens in Mantic and
@Mitsuya Shibata: Well, yes it *affects* Japanese fonts too, but it
makes no sense that *this change* would increase the risk of picking
Chinese glyphs under a Japanese locale.
OTOH, if I start Firefox with:
env LC_CTYPE=ja_JP.UTF-8 firefox
the default sans-serif font for me according to FF
** Attachment added: "jammy glyph"
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5683253/+files/Screenshot%20from%202023-07-01%2021-52-33.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Hi all,
Does this fix affect Japanese fonts?
I installed Ubuntu 23.04 today and encountered a problem where the
Japanese in the snap package is incorrectly displayed with Chinese font
glyphs.
Specifically, the problem occurs in Firefox and Snap Store, but not in
gnome-terminal or Text Editor.
No worry, now things make sense, thanks for testing and confirming it's
fixed!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/2017076
Title:
default Chinese font in snap
@Sebastien: Sorry for confusing the installer with the ISO (which is
used for installing...).
My point was that at first login after a Chinese install, you have the
versions of firefox and core22 from April, and thus see the issue if you
open FF before having refreshed the snaps.
One concern of
> The first screenshot after the description is one from firefox showing
an issue, reading the comments my understanding is that the report was
about the firefox issue which has been resolved now
Yes :)
--
You received this bug notification because you are a member of Desktop
Packages, which
> The installer is mentioned in the first sentence in the bug
description. :)
No it isn't? The description states 'After installs Ubuntu 23.04 with
Chinese language' which refers to the installed system and not the
installer? (just to be clear to me 'installer' is ubuntu-desktop-
installer in
The installer is mentioned in the first sentence in the bug description.
:)
I was thinking that the installer still ships the old snap without the
fix. Then, if the user opens FF before refreshing the snaps, they would
still have the wrong default in FF.
Maybe I'm wrong. I haven't done any
@Gunnar, what's the issue with the installer? it's the first time the
installer is mentioned on that report so I'm not sure to understand the
question
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
This seems to be fixed in Firefox latest/stable/ubuntu-23.04 114.0.1.
@Sebastien: But that doesn't fix the 23.04 installer, does it?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
I've proposed a fix for the core22 serie now on
https://github.com/ubuntu/gnome-sdk/pull/143
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/2017076
Title:
default Chinese
** Changed in: fontconfig (Ubuntu)
Importance: High => Undecided
** Changed in: fontconfig (Ubuntu)
Status: New => Invalid
** Changed in: language-selector (Ubuntu)
Status: New => Invalid
** Changed in: snappy
Status: New => Confirmed
--
You received this bug
On 2023-04-21 21:18, Sebastien Bacher wrote:
> @Gunnar, that's because the only channel which has the core22
> firefox atm is stable/ubuntu-23.04 (which is specific to Lunar).
So, then I just learned that if you are on lunar aka 23.04 and install
firefox from the latest/stable channel, you get
Oh, I miss that the lunar desktop image installs firefox snap from
latest/stable/ubuntu-23.04 branch.
So, if I install firefox from latest/stable channel (which uses core20),
then Noto CJK is rightfully selected.
--
You received this bug notification because you are a member of Desktop
@Gunnar, that's because the only channel which has the core22 firefox
atm is stable/ubuntu-23.04 (which is specific to Lunar). We transitioned
Lunar to core22 but we still need to work with Mozilla on updating the
other channels
Your testing suggest that the issue was the one I mentioned earlier
This is confusing. If you install Ubuntu 23.04, you get FF from
latest/stable/23.04 together with core22.
Now I did a test where I removed FF, set the zh_CN.UTF-8 locale, and
installed FF again. Whichever channel I pick (tried latest/stable,
latest/beta and latest/edge) it pulls core20, and then
@seb128, I think you mean esr/stable channel?
esr channel which uses core20 is using Noto font.
See the attachment.
** Attachment added: "screenshot"
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5666489/+files/2023-04-22_00-34.png
--
You received this bug
Do you get the same issue on core20 snaps (like firefox from the stable
channel)?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/2017076
Title:
default Chinese font in snap
I had an IRC conversion with Sebastien Bacher and learned that things no
longer work as I thought they did. Unlike what I thought, the snaps do
no longer honor the font configuration of the host system, but live in
their own world in this respect.
Adding the language-selector package, since many fontconfig files
affecting Chinese rendering are provided by language-selector-common.
** Also affects: language-selector (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
One thought is to ask why we still install the fonts-arphic-uming
package when installing Chinese (Simplified as well as Traditional).
Probably it is of historical reasons from the time before Noto existed.
But let's consider that to be a matter of its own. Even if AR PL UMing
is available, Noto
29 matches
Mail list logo
