> A good command to use for these situations is locale(1).
> Note, the double quotes in the output are significant, as the fine man
> page explains.
Hi Ralph,
thanks for the tip! I wasn't aware of this command previously, and
I'm reading through the man right now.
--
"That gum you like i
> "I forgot to generate the locales" will cause this issue. Try running
> `localedef --list-archive` and checking that en_CA.UTF-8 actually exists.
> If not, uncomment it in /etc/locale.gen and run `sudo locale-gen`.
Right on the mark, Mr. Celti,
I discovered this mere minutes before your mail.
P
> The ls command will by default escape the character into its numeric
> code if it thinks the character is invalid in your locale. I can get ls
> to print the same thing as you (using shell-escaped $'\303\251') *iff* I
> first export LC_ALL=C (which is not a UTF-8 locale and therefore cannot
> pri
> What happens if you run the following?
>
> $ echo $'\303\251'
>
> I get the character printing correctly.
Same here, it prints out fine. Terminal is Konsole.
I tried touching new file with é, and ls again prints the escape
sequence, however - trying to `cat` the file by hitting Tab to get
aut
> There might also be a difference between libreoffice-fresh and
> libreoffice-still which is quite a bit behind fresh.
Hi Gene,
also a good idea, I wasn't even aware of the `libreoffice-still`
package.
I tried replacing `libreoffice-fresh` with it, and I still get the
same error,
> Can you determine some steps that exactly reproduce the problem?
> Assuming that the problem should manifest when opening the file using
> /usr/bin/loffice /path/to/file, I tried creating a test file and opening
> it, and it worked:
Hi Eli,
good idea, I tried following your sequence as well.
item.decode('utf8')
> except UnicodeDecodeError:
> print(item, "is not valid UTF8")
> raise
>
> On Fri, Aug 2, 2019 at 12:48 PM Eli Schwartz via arch-general <
> arch-general@archlinux.org> wrote:
>
> > On 8/2/19 8:59 AM, J
> Good jump on the research.
I try to do what I can, before asking other people to spend their time
on me :-)
> I don't have a direct answer, but check the version(s) of LibreOffice,
> Dropbox, and possibly some of the other packages you've already
> mentioed. Perhaps your issue is something tha
Hi everyone,
there's a document on Dropbox, that has unicode character in its
path (french character). Trying to open this document with libre
office (Plasma is running) fails with 'file not found', and the path
shown with error clearly presents the path with that unicode
charac
9 matches
Mail list logo
