inputenc and latin1
zunbeltz
I've some trouble with this simple code. I've use it on windows (wiht miktex)
without problems, but now I'm using linux (Suse 8.1) and it doesn't woirk
the code:
\documentclass[12pt,a4paper]{article}
\usepackage[latin1]{inputenc}
\usepackage[OT1]{fontenc}
\usepackage[spanish]{babel}
\begin{document}
\title{Organización}
\author{Zunbeltz Izaola}
\date{\today}
\maketitle
\end{document}
the log error is:
! Package inputenc Error: Keyboard character used is undefined
(inputenc) in inputencoding `latin1'.
the problem is the "o" with accent, but i don't know why
Zunbeltz
Rolf Niepraschk
> Hi
>
> I've some trouble with this simple code. I've use it on windows (wiht miktex)
> without problems, but now I'm using linux (Suse 8.1) and it doesn't woirk
>
> the problem is the "o" with accent, but i don't know why
Try:
\usepackage[T1]{fontenc}
...Rolf
--
|| Rolf Niepraschk c/o Physikalisch-Technische Bundesanstalt ||
|| Abbestr. 2-12; D-10587 Berlin, Germany ||
|| Tel/Fax: ++49-30-3481-316/490, email: niepr...@ptb.de ||
Robin Fairbairns
it works here[*], so either:
-- you've copied (rather than included) something that was in an
eccentric character set, where "ó" had a different position, or
-- you've got a corrupt copy of latin1.def
[*] apart from the diagnostic about spanish hyphenation patterns,
which i don't have. you do realise that you won't get decent
hyphenation using ot1 fonts?
--
Robin Fairbairns, Cambridge -- the man with no voice (_again_)
David Kastrup
> zunl...@hotmail.com (zunbeltz) writes:
> >without problems, but now I'm using linux (Suse 8.1) and it doesn't woirk
> >
> >the code:
> >\documentclass[12pt,a4paper]{article}
> >\usepackage[latin1]{inputenc}
> >\title{Organización}
> >! Package inputenc Error: Keyboard character used is undefined
> >(inputenc) in inputencoding `latin1'.
> >
> >the problem is the "o" with accent, but i don't know why
>
> it works here[*], so either:
>
> -- you've copied (rather than included) something that was in an
> eccentric character set, where "ó" had a different position, or
> -- you've got a corrupt copy of latin1.def
Or SuSE has changed its default character set to something different
from Latin-1.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
UKTUG FAQ: <URL:http://www.tex.ac.uk/cgi-bin/texfaq2html>
Bernd Strieder
> I've some trouble with this simple code. I've use it on windows (wiht
> miktex) without problems, but now I'm using linux (Suse 8.1) and it
> doesn't woirk
No problem here using SuSE 8.1. Is it possible that the text itself was not
latin1, but somehow worked on windows. What does the text look like viewed
at the command-line on linux, e.g. with cat, less or vi?
> ! Package inputenc Error: Keyboard character used is undefined
> (inputenc) in inputencoding `latin1'.
Bernd Strieder
Lars Madsen
type latin-1
then a similar problem worked for us.
/daleif
zunbeltz
> zunbeltz wrote:
> > I've some trouble with this simple code. I've use it on windows (wiht
> > miktex) without problems, but now I'm using linux (Suse 8.1) and it
> > doesn't woirk
>
> No problem here using SuSE 8.1. Is it possible that the text itself was not
> latin1, but somehow worked on windows. What does the text look like viewed
> at the command-line on linux, e.g. with cat, less or vi?
The text was typed with Emacs, and i think the problem is there. The
text dosn't looked right in vi (instead of "ó" apear a number - 255 i
think). I know that this is not the best group to ask it, but, someone
can point me to some regerence about encodings ( expecialy encodings
in Emacs and Linux/Unix utilites to traslates files from one encoding
to another)
Thanks
Zunbeltz
David Kastrup
> Bernd Strieder <stri...@informatik.uni-kl.de> wrote in message news:<asi8or$ah6$1...@news.uni-kl.de>...
> > zunbeltz wrote:
> > > I've some trouble with this simple code. I've use it on windows (wiht
> > > miktex) without problems, but now I'm using linux (Suse 8.1) and it
> > > doesn't woirk
> >
> > No problem here using SuSE 8.1. Is it possible that the text itself was not
> > latin1, but somehow worked on windows. What does the text look like viewed
> > at the command-line on linux, e.g. with cat, less or vi?
>
> The text was typed with Emacs, and i think the problem is there. The
> text dosn't looked right in vi (instead of "ó" apear a number - 255 i
> think). I know that this is not the best group to ask it, but, someone
> can point me to some regerence about encodings ( expecialy encodings
> in Emacs and Linux/Unix utilites to traslates files from one encoding
> to another)
Well, load the file, then ask Emacs what it thinks the encoding is
(with C-h C RET) for saving the file is. You can change that with
C-x C-m f latin-1-unix RET
then save again.
And it might be worth finding out why Emacs did what it did. What
did C-h C RET tell you about the default coding system?
What is the output of
locale
in your shell?
zunbeltz
> (with C-h C RET) for saving the file is. You can change that with
> C-x C-m f latin-1-unix RET
> then save again.
>
> And it might be worth finding out why Emacs did what it did. What
> did C-h C RET tell you about the default coding system?
>
This is what Emacs thinks about the default coding system:
Coding system for saving this buffer:
1 -- iso-latin-1-unix
Default coding system (for new files):
1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
Coding system for keyboard input:
nil
Coding system for terminal output:
0 -- iso-latin-9 (alias: iso-8859-15 latin-9 latin-0)
Defaults for subprocess I/O:
decoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
encoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
Priority order for recognizing coding systems when reading files:
1. iso-latin-1 (alias: iso-8859-1 latin-1)
2. iso-2022-jp (alias: junet)
3. iso-2022-7bit
4. iso-2022-7bit-lock (alias: iso-2022-int-1)
5. iso-2022-8bit-ss2
6. emacs-mule
7. raw-text
8. japanese-shift-jis (alias: shift_jis sjis)
9. chinese-big5 (alias: big5 cn-big5)
10. no-conversion (alias: binary)
11. mule-utf-8 (alias: utf-8)
Other coding systems cannot be distinguished automatically
from these, and therefore cannot be recognized automatically
with the present coding system priorities.
The followings are decoded correctly but recognized as iso-2022-7bit-lock:
iso-2022-7bit-ss2 iso-2022-7bit-lock-ss2 iso-2022-cn iso-2022-cn-ext
iso-2022-jp-2 iso-2022-kr
Particular coding systems specified for certain file names:
OPERATION TARGET PATTERN CODING SYSTEM(s)
--------- -------------- ----------------
File I/O "\\.elc\\'" (emacs-mule . emacs-mule)
"\\(\\`\\|/\\)loaddefs.el\\'"
(raw-text . raw-text-unix)
"\\.tar\\'" (no-conversion . no-conversion)
"" (undecided)
Process I/O nothing specified
Network I/O nothing specified
> What is the output of
>
> locale
>
> in your shell?
LANG=es_ES@euro
LC_CTYPE="es_ES@euro"
LC_NUMERIC="es_ES@euro"
LC_TIME="es_ES@euro"
LC_COLLATE=POSIX
LC_MONETARY="es_ES@euro"
LC_MESSAGES="es_ES@euro"
LC_PAPER="es_ES@euro"
LC_NAME="es_ES@euro"
LC_ADDRESS="es_ES@euro"
LC_TELEPHONE="es_ES@euro"
LC_MEASUREMENT="es_ES@euro"
LC_IDENTIFICATION="es_ES@euro"
LC_ALL=
Zunbeltz
David Kastrup
> This is what Emacs thinks about the default coding system:
> Coding system for saving this buffer:
> 1 -- iso-latin-1-unix
> Default coding system (for new files):
> 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
How comes Emacs thinks this? Have you set the default language
environment somewhere?
> Coding system for terminal output:
> 0 -- iso-latin-9 (alias: iso-8859-15 latin-9 latin-0)
So Emacs knows that you have a Latin-9 terminal...
> Priority order for recognizing coding systems when reading files:
> 1. iso-latin-1 (alias: iso-8859-1 latin-1)
But it would not recognize a Latin-9 file when coming across it...
> > What is the output of
> >
> > locale
> >
> > in your shell?
> LANG=es_ES@euro
> LC_CTYPE="es_ES@euro"
And that is a Latin-9 coding system...
Personally, I have switched my system from Latin-9 or even utf8
completely back to Latin-1 and will keep it that way until I am
reasonably sure Emacs will be fine with that in all respects I could
imagine (including when starting something like x-symbol or LaTeX or
such).
Encoded mail/news will display the Euro character and even utf8 files
fine as long as I use X11, and that is most of what would matter for
me.
Of course, things should work just the same, but not all important
packages/tools of me seemingly do so perfectly.
zunbeltz
> zunl...@hotmail.com (zunbeltz) writes:
>
All the problem was that the LANG enviroment variable was not set approperly.
I've put the iso-8859, and all is going well. Thank you for your information
and patience :-)
Zunbeltz
Robin Fairbairns
>All the problem was that the LANG enviroment variable was not set approperly.
>I've put the iso-8859, and all is going well. Thank you for your information
>and patience :-)
i hope you've put slightly more than that in: iso 8859 is (so far) a
15-part standard (iirc -- not all parts are currently populated, i
think). most people from western europe (or speaking a w.e.-derived
language) use iso 8859-1 (latin1), though we can probably expect iso
8859-15 (latin9) to take over sooner or later, being as how it has a
euro sign in it.
zunbeltz
> i hope you've put slightly more than that in: iso 8859 is (so far) a
> 15-part standard (iirc -- not all parts are currently populated, i
> think). most people from western europe (or speaking a w.e.-derived
> language) use iso 8859-1 (latin1), though we can probably expect iso
> 8859-15 (latin9) to take over sooner or later, being as how it has a
> euro sign in it.
export LANG=es_ES.ISO-8859-1
I only had to comment out this line in my .profile.
Zunbeltz Izaola