public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24045] LC_ADDRESS for i18n might not match ISO/IEC 14652
Date: Wed, 02 Jan 2019 12:35:00 -0000	[thread overview]
Message-ID: <bug-24045-716-KNaOGkrx80@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24045-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24045

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
           See Also|                            |http://bugs.debian.org/9133
                   |                            |48
              Flags|                            |security-

--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
I think we should deprecate most parts of LC_ADDRESS because the data model is
not correct.  ISO/IEC TR 14652:2002 does not improve things, I'm afraid.

The key problem is the assumption of a single address format per locale, which
I doubt is correct for any country.  For example, in Germany, there are valid
postal addresses which lack a street, and the definition of %N in the TR
results in leading spaces before the zip code in this case.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2019-01-02 12:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24045-716@http.sourceware.org/bugzilla/>
2018-12-30 23:42 ` aurelien at aurel32 dot net
2019-01-02 12:35 ` fweimer at redhat dot com [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-24045-716-KNaOGkrx80@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).