Stefan Förster writes:
> If changing a language definition like that, doesn't that mean one
> will have to change the various predefined template files, all message
> codes for that language and after that recreate the archive files?
Normally, yes. But this is *English*. It's reasonably like
* Mark Sapiro wrote:
> Stephen J. Turnbull wrote:
>
>> Mark Sapiro writes:
>>
>>> add_language('en', 'English (USA)', 'utf-8', 'ltr')
>>
>> Shouldn't this probably be default by now?
>
>
> Yes, it should. But, we have superstitious beliefs that something
> unintended will be broken by this. Y
Barry Warsaw writes:
> On Mar 28, 2009, at 10:23 AM, Mark Sapiro wrote:
> > Yes, it should. But, we have superstitious beliefs that something
> > unintended will be broken by [setting the default encoding to
> > UTF-8].
Oh, me too! The Ghost of Charsets Past will undoubtedly rise up to
remind
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 28, 2009, at 10:23 AM, Mark Sapiro wrote:
Stephen J. Turnbull wrote:
Mark Sapiro writes:
add_language('en', 'English (USA)', 'utf-8', 'ltr')
Shouldn't this probably be default by now?
Yes, it should. But, we have superstitious belief
Stephen J. Turnbull wrote:
>Mark Sapiro writes:
>
> > add_language('en', 'English (USA)', 'utf-8', 'ltr')
>
>Shouldn't this probably be default by now?
Yes, it should. But, we have superstitious beliefs that something
unintended will be broken by this. Yet, I continue to suggest it as a
workarou
Mark Sapiro writes:
> add_language('en', 'English (USA)', 'utf-8', 'ltr')
Shouldn't this probably be default by now? I'm usually pretty
hesitant to mess with existing defaults, but as I understand this
there's actually corrupt data in the .txt files. This can be a real
headache for people usin
Drew Tenenholz wrote:
>
>The list is a announce-only type in Russian (Cyrillic), but the
>default language is set to English (so I can read the admin pages and
>complete the necessary tasks). As I believe Mark mentioned before,
>this means that the messages themselves (sent by the Russian
>Mod
