search for: en_uk

And let's also spell things properly! Like 'internationalisation' ...'Weasels have got into your phone system' instead of 'gotten into your phone system...' And 'please press the hash key..' instead of 'pound key' There should probably be en_uk, en_us, en_ca, en_za, en_nz, en_oz, en_ie and en_in etc to allow each English-speaking country to localise prompts. Just my two pence worth! Rgds Tim -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Olle E. Johans...

R 0.65.0 (and all others I have seen), Solaris 2.6. > sort(c("a", "A", "b", "B")) [1] "A" "a" "B" "b" > "a" < "B" [1] FALSE in the en_UK locale. I don't think it is good idea that sort and < have a different idea of ordering, so I rate this as a bug. As far as I can see sort uses strcoll and hence the locale, and < uses ASCII. -- Brian D. Ripley, ripley@stats.ox.ac.uk Professor of Applied Statistics, ht...

I use R CMD Rdindex man/*.Rd >INDEX in my makefile to generate an INDEX. When I then use R CMD build whatever the newindex seems to be in a slightly different order, resulting in a * checking whether index is up-to-date ... NO (because the result of diff is not empty) and a suggestion to use --force. However, --force results in the INDEX in my source directory being re-written, which

...ntical(Sys.setlocale("LC_CTYPE", mbyte.lc), mbyte.lc)) >> oloc > [1] "en_US.UTF-8" >> mbyte.lc > [1] "en_US.UTF-8" I had been making these changes in R-devel after offline discussions with Linux users for which the original check (using "en_UK.UTF-8") failed. What I read below is suggesting that "C.UTF-8" is not okay either, as a fallback. It seems we should use "en_US.UTF-8" as fallback instead (though I assume that won't work in North Korea). I've committed a version that does that _and_ no longer st...

On RedHat Enterprise Linux 6, the test below fails (this is using the stock GCC 4.4.7) from R-devel r72707. LC_CTYPE is unset when I run it, but LANG=en_US.UTF-8 It also failed "yesterday" where as far as I recall the test code looked a bit different. Best, Kasper > ## Results differed by platform, but some gave incorrect results on string 10. > > > ## str() on large