Hello,
>> I am working with LANG=de_DE@euro.
>Don't do that then, swwitch to .UTF-8. It's not 2002 anymore. And
>I'd think that many other things at least assume UTF8 per default. Especially
>since Debian defaults to UTF-8 since loong, too.
It well may be that utf-8 is selected per default. But this does not mean, it
is the only working locale. Or is there any statement from Debian that all other
locales have been dropped?
>> It seems with LO 4.1.5.3 (Debian 8) this is not needed any more.
>There's no Debian 8 (yet).
Yes the version I (have to) use is from weekly builds. Not stable, of course,
but it works (nearly) well.
One reason for my report is the hope the locale issues will be solved in the
final release of Debian 8.
>> D [08/Apr/2014:09:17:57 +0200] Create-Job
>> client-error-attributes-or-values-not-supported: Bad job-name value:
>> "job-name": Bad name value "Erläuterungen" - bad UTF-8 sequence (RFC 2911
>> section 4.1.2).
> (and this is with cups, not LOm, so irrelevant here)
No. As the message says, CUPS wants an utf-8 encoded value. It is the task of
LO to
build and send it.
Like all other software LO cannot rely on working in a special locale. Or
otherwise
it should refuse to start when it detects an unsupported one.
If you are interested, you may read a memo I have written some time ago:
"How to change the locale from iso8859-1 to utf-8 on a Linux workstation
(or why this is not as simple as some programmers think)"
http://fserver.alburg.selfhost.me/Linux-Locales/Locale%20change.html
Markus
--
To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/trinity-a3c90a87-6917-4349-a499-33e1564fff0d-1397550703659@3capp-gmx-bs63
