** Changed in: snapd
Status: Confirmed => Triaged
** No longer affects: snapcraft
** Changed in: snapd
Importance: Undecided => Medium
** Changed in: snapd (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I wonder if my `locales-launch` remote part can workaround this issue at the
snap end?:
https://forum.snapcraft.io/t/the-locales-launch-remote-part/8729
Also according to the discussion at https://forum.snapcraft.io/t/lack-
of-compiled-locales-breaks-gettext-based-localisation/3758 , can't we
jus
The issue is in the core snap which does not provide the required locale
data, forcing applications to attempt to do it themselves, which is not
easy to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
@chipaca
The issue that remains is that applications that need UTF-8 require
workarounds in the snap.
This issue explains it in more detail with an example in python:
https://bugs.launchpad.net/snapcraft/+bug/1804845
Basically, the issue is that stuff like $LANG gets passed into the snap,
but th
@eri0 that depends on exactly which "this" you mean :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title:
UTF-8 is not very well supported inside snaps
To manage notifications about this
Was this ever solved?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title:
UTF-8 is not very well supported inside snaps
To manage notifications about this bug go to:
https://bugs.launchpad
** Also affects: snapcraft
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title:
UTF-8 is not very well supported inside snaps
To manage notificat
If we're doing this, we should have a core config as to what locales to
generate. That way on small core devices we just generate what's needed
(often: nothing). On non-core we can make that unsettable and proxy to
whatever the host uses for the 'get' step.
--
You received this bug notification b
If one is calling locale-gen on the first app invocation, it seems plausible on
install snapd could:
1. do the equivalent of 'snap run --shell .'
2. run locale-gen
3. exit the shell and use 'snap-discard-ns '
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@zyga
i think you would have to call locale-gen on first start of each app
(depending on the CPU power of your system that can take quite a while),
not sure you can hack around this easily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
(alternatively snapcraft could call it and generate *all* possible
locales (well, the UTF-8 variant) for the app and have it shipped in the
snap)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
>From a desktop POV, can we reuse the locale data available on the host
somehow? If snapd on classic were to bind mount /usr/share/locale from
the host into the snap space (and somehow, which is tricky, merged it
with locale data from core and the app snap) would that be the desired
outcome?
On co
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title:
UTF-8 is not very well supported inside snaps
To manage notifications
https://bitbucket.org/flexiondotorg/podpublish/src/4fce812d64149151d97d2bba6bc46bc6595f682f/snapcraft.yaml?at=master&fileviewer
=file-view-default#snapcraft.yaml-15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
A few more sightings, that require the workaround:
https://github.com/21dotco/two1-python/pull/16/files#diff-
184032a532406b07009403e26f4fc62fR13
https://github.com/warner/magic-wormhole/blob/master/snapcraft.yaml#L21
--
You received this bug notification because you are a member of Ubuntu
Bugs
Same problem in errbot, and same workaround to force LC_ALL=C.UTF-8:
https://github.com/elopio/errbot/blob/snapcraft/snapcraft.yaml#L14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title:
U
I had to workaround this issue as well for conjure-up by exporting
LC_ALL=C.UTF-8 (https://github.com/conjure-up/conjure-
up/tree/master/snapcraft).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157641
@ogra, thank you for your example from nethack! I hit the same issue
with a simple python3 script that was failing due to
sys.getfilesystemencoding() returning 'ascii'. Modifying my wrapper to
do the following:
export LOCPATH=$SNAP_USER_DATA
LANG=en_US
ENC=UTF-8
LOC="$LANG.$ENC"
if [ ! -e $SNAP_
@ralsina, yeah, that was more a "how it once worked" example :)
i have update (and uploaded) nethack now at
https://github.com/ogra1/nethack/blob/master/nethack.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Any more progress on actually fixing this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title:
UTF-8 is not very well supported inside snaps
To manage notifications about this bug go
The workaround by Oliver doesn't wok for me, apparently because the
environment variable names have changed?
Here's a version that is working for me with snapcraft 2.11, snapd 2.0.8
https://github.com/getnikola/nikola/blob/provide-
snap/snapcraft/nikola.sh
--
You received this bug notification
for the non bindtextdomain snaps (i.e. any binaries that just use libc's locale
functions)
line 7-21 in
http://bazaar.launchpad.net/~ogra/+junk/nethack/view/head:/nethack.sh
plus the libc-bin and locales packages in "stage-packages" are a
solution if you want to ship your own locales inside the
I made a question in askubuntu, a comment linked me to here.
http://askubuntu.com/questions/783758/self-built-snap-run-fail-on-
locale-error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title
bug #1576303 is about font since that was mentioned as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title:
UTF-8 is not very well supported inside snaps
To manage notifications about
On a similar note we(desktop) opened bug #1576282 "Snaps built from deb
can't be gettext translated" with that note
"- traditional desktop applications are built with calls to
'bindtextdomain ("domain", LOCALEDIR)', where LOCALDIR is defined at
buildtime and so pointing to /usr
there seems to be
> how would a snap access the desktop locales ?
I talked to mvo about this today. It sounds like there are two ways to
deal with this: either bind-mount the desktop locales into the ubuntu-
core snap, or bound-mound them into /classic in the ubuntu-core snap and
redirect things accordingly. I gues
This is an interesting one. We definitely want to be GREAT for IoT, we
also want to become the best way to deliver a desktop app. The latter
means that locales need to be workable.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
how would a snap access the desktop locales ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title:
UTF-8 is not very well supported inside snaps
To manage notifications about this bug go to
> perhaps the ubuntu-core-launcher should enforce C-UTF-8 for all snaps
...
That would enforce it on the desktop as well, where we do have locales.
Would that be an issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
this is due to the fact that snappy does not ship any locale data except
C and C.UTF-8 ... nor any fonts or keymaps ... given that we fully focus
on embedded and IoT with the rootfs
perhaps the ubuntu-core-launcher should enforce C-UTF-8 for all snaps
...
--
You received this bug notification be
Here's the snap for the 2nd example.
** Attachment added: "ola_1_amd64.snap"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1576411/+attachment/4654249/+files/ola_1_amd64.snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you please attach a snap that shows this to happen?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title:
UTF-8 is not very well supported inside snaps
To manage notifications about this
I can confirm the hello-world case. It is quite curious, not sure what
to make of it yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title:
UTF-8 is not very well supported inside snaps
** Also affects: snappy
Importance: Undecided
Status: New
** Changed in: snappy
Status: New => Triaged
** Changed in: snappy
Importance: Undecided => High
** Changed in: snappy
Milestone: None => sru-2
** Changed in: snapd (Ubuntu)
Status: New => Triaged
** Chang
34 matches
Mail list logo
