This behavior make totally useless the language selector.

however, i’m not so sure that the keyboard language should be regarded as a precise indicator of the language you’re typing in:

— i use a custom keyboard layout based upon us english, even when i type in romanian, using â, ă, î, ș, ț etc.
— moreover, i believe that most romanians use us/uk english as the keyboard language, for the simple fact that romanian keyboards are not so common.

why does port 80 need to be enabled?
I have Tomcat installed port 8080 and httpd on port 80, want to install Hudson now, but — being a newbie – afraid to mess with things that are working at the moment (Tomcat installation working).

Thanks in advance for any explanation!

Here is a proposed evaluation for SPIP 2 :

1.1 Page language : YES
1.2 Pages not existing in base language : YES
1.3 Different menus : YES
1.4 Draft or test mode, a way to test the translation to a new language but without showing it to the normal site visitors : YES
2.1 Linking to untranslated pages : YES
2.3 Links updated when translation added : NO
2.4 Links updated when translation removed : NO
2.5 Redirect on page rename : NO
2.6 Links updated instead of redirects : I would say yes : Links shortcuts refer to ID not to URL
2.7 Easy linking : NO
3.1 Custom URL : YES
3.2 Custom html title : YES
3.3 Custom html keywords : YES
3.4 Language selection from URL : depends of the context.
4.1 Search on all pages, not only current language : YES
4.2 Auto detect new visitor language and redirect it if requested page has proper translation : NO

You may want to mention in the articles the score card items your text refer to : it is not always explicit.

so if you check if [NSEvent charactersIgnoreModifiers] == ‘a’ along with [NSEvent modierFlags]. you should be able to tell cmd+A on all keyboard layouts.

Right?