[Dict-common-dev] Re: Bug#278747: dictionaries-common: Please support iso-8859-15

[Agustin Martin]

Sending again this message,

On Fri, Nov 05, 2004 at 01:01:53AM +0100, Agustin Martin wrote:

> If there are no objections or somebody propose something better I plan
> to include iso-8859-15 in ispell.el at some time in next week, and
> modify the policy for that.

Now that emacs20 is no longer in sarge I am considering something
even less restrictive, allowing all encodings supported by emacs, using a  
suggestion by Joao Cachopo for ispell.el in the #208518  thread.

This the draft of the new wording for the relevant section. Comments are
welcome.

-----------------------------------------------------------------------
  * Coding-System : (optional, defaults to the empty string)

    Used for languages with multibyte characters. Any coding system
    will be accepted if the {x}emacs version being run accepts it.
    Maintainers, please check that the provided coding system works
    with the different emacsen flavours. If the coding system is not
    one of iso-8859-1, iso-8859-2, iso-8859-3 or koi8-r make your
    package depend on at least dictionaries-common (>=0.24), where
    the other encodings were allowed.


+--------------------------------------------------------------------+
|                              Warning                               |
|--------------------------------------------------------------------|

   At the time of this writing there are some encoding unification
   problems in emacs between iso-8859-1 and iso-8859-15 charsets,
   being the same character represented differently in the emacs
   internal mule encoding. For this reason please do not blindly
   replace the old iso-8859-1 entry by iso-8859-15. If you require
   the iso-8859-15 encoding, better add a new emacs only iso-8859-15
   entry (see debconf-display: no) as a temporary workaround. This
   way the iso-8859-1 entry will work with iso-8859-1 and UTF-8 texts
   and fail with iso-8859-15, while the new iso-8859-15 entry will
   work with iso-8859-15, but will fail with iso-8859-1 and UTF-8.
   The same might also apply to other charsets, please doublecheck.

-----------------------------------------------------------------------

Cheers,

-- 
Agustin