On Mon, Aug 4, 2014 at 5:55 PM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum 10353@lyskom.lysator.liu.se wrote:
I haven't checked whether the changes to the codepages that you suggest make sense yet (the current tables are generated from RFC1345, so if there is a discrepancy it should be investigated more closely), but I don't really see any point in adding your script to the repository...
Yeah, that's why I kept that separate. Figured it quite possibly wouldn't be useful :)
Poking around on the internet showed up other places where RFC 1345 is discussed due to incompatibilities with current Unicode standards, such as this thread (highlights only):
http://www.ietf.org/mail-archive/web/ietf/current/msg47378.html http://www.ietf.org/mail-archive/web/ietf/current/msg47387.html http://www.ietf.org/mail-archive/web/ietf/current/msg47444.html http://www.ietf.org/mail-archive/web/ietf/current/msg47574.html
It seems that, in the event of a conflict, the Unicode files should be used rather than RFC 1345, which has been reported as having errors.
ChrisA
http://www.ietf.org/mail-archive/web/ietf/current/msg47378.html http://www.ietf.org/mail-archive/web/ietf/current/msg47387.html http://www.ietf.org/mail-archive/web/ietf/current/msg47444.html http://www.ietf.org/mail-archive/web/ietf/current/msg47574.html
These posts appear to be about the _names_ assigned to characters in RFC 1345, which isn't relevant here.
pike-devel@lists.lysator.liu.se