[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] Country codes
On 01/09/13 13:24, Vincent Rivière wrote:
On 09/01/2013 11:57, Alan Hourihane wrote:
I think there's more chance of breaking existing code that's been long
standing in XaAES, than EmuTOS.
Is this true?
As I saw, the integer codes are only used internally by XaAES, they
don't affect the user experience or configuration files.
Moreover, there was the kernel bug I fixed recently which prevented
using country codes >= 6 from the NVRAM.
So I can't see any scenario where changing the FreeMiNT country codes
could break something.
What about the _AKP cookie. Applications could use that value, and am I
right in thinking these language values would already have been
advertised to applications, regardless of XaAES ?
However, new information from Helmut:
The number is returned in appl_getinfo.
I don't know how much this is important.
I'm sure lots of apps use that.
It's only come to light because there's probably more people testing
EmuTOS snapshots in these countries than those testing XaAES snapshots
in these countries.
Actually, no one noticed.
I saw that issue by looking in both EmuTOS and FreeMiNT sources.
So, I'm not sure what that means then.
How many people are affected in EmuTOS ?
I don't know.
I have invited the relevant people to join the discussion here.
O.k.
Alan.