bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug#110416: Error while loading 50gettext


From: Santiago Vila
Subject: Re: Bug#110416: Error while loading 50gettext
Date: Sat, 9 Mar 2002 00:38:03 +0100 (CET)

Chaskiel M Grundman wrote:
> Has there been any progress on this? The base cause of the problem seems to
> be that non-mule xemacs doesn't have modify-coding-system-alist.
> (xemacs21-mule loads the file just fine)

The suggestion in gettext-0.11 about what to put in .emacs has not changed
in a significant way from gettext-0.10.40:

------------------------------------------------------------------------
If you are using Emacs version 20 or newer, and have already installed
the appropriate international fonts on your system, you may also tell
Emacs how to determine automatically the coding system of every PO file.
This will often (but not always) cause the necessary fonts to be loaded
and used for displaying the translations on your Emacs screen.  For this
to happen, add the lines:

@example
(modify-coding-system-alist 'file "\\.po\\'\\|\\.po\\."
                            'po-find-file-coding-system)
(autoload 'po-find-file-coding-system "po-mode")
@end example
------------------------------------------------------------------------

The 50gettext.el file provided by the Debian package in the site-start.d
directory does this.

I think it's a good default because it's appropriate for most users,
and I believe it's resonable that people for which this default is not
good enough change it to suit their own needs.

However (this is a question for the gettext maintainers), is there a
default file to use which has this functionality for people using
emacs20 or later and does not give an error when using xemacs21-non-mule?

(In other words: Is there a simple way to improve this default file?)

[ I could also use the flavor-dependent directories /etc/emacs20,
/etc/emacs21, etc. and put different files in each of them, but not being
an emacs lisp guru, it would become a nightmare to maintain. I don't think
it would be a good idea ].

[ The complete details about this bug should be found in the following URL: ]

http://bugs.debian.org/110416





reply via email to

[Prev in Thread] Current Thread [Next in Thread]