There is a PPA for the snapshot

https://launchpad.net/~cassou/+archive/emacs

http://emacs.naquadah.org/ (Debian)

Complete list http://www.gnu.org/software/emacs/NEWS.24.1

You can also find out about the important changes from:

  C-h r m antinews RET

This provides a changelog in the opposite direction, which is entertaining:

  For those users who live backwards in time, here is information about
  downgrading to Emacs version 23.4.  We hope you will enjoy the greater
  simplicity that results from the absence of many Emacs 24.1 features.

-----

It can be found online here:

http://www.gnu.org/software/emacs/manual/html_node/emacs/Ant...

They could add support for GCC (MinGW) and ship it.

No APL code? I'm disappointed!

Can you elaborate on that? Why does Unicode suck for Japanese text?

Not only kanji, but also hiragana and katakana (syllabic alphabets) encode to three bytes per character. Shift-JIS can encode all three to two bytes, as well as half-width katakana to one byte per character.

However, if size is such a concern (eg for web transmission), text compression neutralizes the perceived benefit of region-specific encodings.

Shift-JIS' continued popularity has much more to do with change aversion than it does technical merit.

As I said above, I spoke with several Japanese people who said that some valid characters are not representable in Unicode.

Some details can be found here: http://en.wikipedia.org/wiki/Han_unification

On the web ASCII (think HTML tags, CSS stylesheets, etc) typically is a large fraction of CJK pages, so the relative inefficiency of UTF-8 for encoding is less important.

@ruediger There's nothing wrong with Unicode. UTF-8 sucks because it ends up taking more space.

@byuu No it doesn't. Try compressing a SJIS text using gzip. Then convert it to UTF-8 and do the same thing. With a "perfect" compressor, there shouldn't be any difference since the information contents are the same, but unfortunately we don't have a perfect compression algorithm that hits the theoretical lower bound for compression.

> Also UTF-8 string can't be cut at arbitrary position.

Neither can be any other kind of Unicode string because of Combining Characters. That's why the Unicode standard (or an Annex) recommends algorithms for text segmentation.

(And if you really need to cut at a certain length then you can easily backtrack and find the beginning of the sequence by looking for the first byte with the MSB = 0)

ICU has some UTF-8 functionality. But ICU is really ugly.

http://userguide.icu-project.org/strings/utf-8

The problem with start ups is that engineering is fun but business and administration is no fun. Nobody is enthusiastic about filling out tax forms and yelling at people because they are missing deadlines. People with experience in administration are rarely looking for a chaotic start up that can't pay a good salary.

Linux and *BSD have a fixed ABI for C++.