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...
Hm, the issue seems to be that RFC1345 does not distinguish between
heavy strokes and double strokes in the box drawing characters. I'll
make a script to go through those and check them.
I wouldn't call it historical revisionism since the license text
proper hasn't changed, only the preamble. LGPL 2.0 and earlier was the
Library GPL; LGPL 2.1 was the first Lesser GPL.
That the preamble refers specifically to 2.1 or newer is revisionism.
I believe src/export_list is missing the following files, which
install.pike tries to install:
/refdoc/doxfilter.sh
/refdoc/doxygen.cfg
And I'd be inclined to fix any acctual errors, rather than blindly
following one or the other. :-)
Just so you know, the MAPPINGS files on unicode.org is not part of
the Unicode standard, so they are no more a standard than RFC 1345 is.
On Tue, Aug 5, 2014 at 6:55 AM, Marcus Comstedt (ACROSS) (Hail
Ilpalazzo!) @ Pike (-) developers forum 10...@lyskom.lysator.liu.se
wrote:
And I'd be inclined to fix any acctual errors, rather than blindly
following one or the other. :-)
Just so you know, the MAPPINGS files on unicode.org is
Oh! Okay. What is the standard? Where would I find an authoritative
set of codepage-to-Unicode character set replacements?
The authority for mapping for a particular codepage would be the owner
of said codepage. So in the case of e.g. IBM 437 it would be IBM.
An owner of a codepage has no
