After reading some more it seems language and country tags alone
aren't enough. Inside the same country, the same language and even the
same culture, different orderings can be used depending on the
ordering objective. As an example, there can be a specific order used
in phone lists and other for
On 6/28/07, Trevor Talbot <[EMAIL PROTECTED]> wrote:
On 6/28/07, Stephane Bortzmeyer <[EMAIL PROTECTED]> wrote:
> > RFCs 4646 and 4647 cover this convention.
>
> No, "language tags" (specified in RFC 4646) use the dash as a
> separator, unlike the POSIX locales. So, it is pt-BR.
Whoops, good cat
On 6/28/07, Stephane Bortzmeyer <[EMAIL PROTECTED]> wrote:
On Thu, Jun 28, 2007 at 08:45:23AM -0700,
Trevor Talbot <[EMAIL PROTECTED]> wrote
a message of 16 lines which said:
> >It seems more natural to use the standard C locale names to me (the
> >usual "pt_PT" and "pt_BR" for Portuguese/Port
On Thu, Jun 28, 2007 at 08:45:23AM -0700,
Trevor Talbot <[EMAIL PROTECTED]> wrote
a message of 16 lines which said:
> >It seems more natural to use the standard C locale names to me (the
> >usual "pt_PT" and "pt_BR" for Portuguese/Portugal culture and
> >Portuguese/Brazil culture) , but I'm ope
--- Trevor Talbot <[EMAIL PROTECTED]> wrote:
> Microsoft has changed the collation data sub-service pack, so for
> practical purposes it's tied to a specific install of Windows unless
> it contains logic to regenerate indexes on the fly.
>
> At this point you realize that what you need is not a ti
On 6/27/07, Jiri Hajek <[EMAIL PROTECTED]> wrote:
> Right now sqlite database files are portable across systems as-is.
> You're proposing they should need to be explicitly prepared for
> transport? Remember, the risk is silent data corruption. This is not
> a trivial matter.
Well, I do unde
Right now sqlite database files are portable across systems as-is.
You're proposing they should need to be explicitly prepared for
transport? Remember, the risk is silent data corruption. This is not
a trivial matter.
Well, I do understand that Unicode standard is quite a complicated
thing, bu
On 6/27/07, Jiri Hajek <[EMAIL PROTECTED]> wrote:
Is it really that big issue that particular implementations can
differ? For example, doesn't VACUUM recreate indexes, so that they
would be accurate after moving to another platform (and if it doesn't,
shouldn't it?).
Right now sqlite database
Unfortunately, Unicode specifies no such thing. There is no such thing
as _the_ Unicode collation, if only because collation rules depend on
locale.
Yes, what I mean is to define how individual locales are identified in
SQLite, like that already suggested 'en_AU', 'tr_TR', etc.
Implementations
Jiri Hajek <[EMAIL PROTECTED]> wrote:
The only argument against this was that individual implementations of
Unicode standard (i.e. mainly internal Windows methods or ICU library)
could differ. However, is it really a problem? I'd say that it isn't.
Unicode specifies exactly how characters should
10 matches
Mail list logo
