Thank you! Yes, that's an implicit part of the "I'd like feedback from the
people involved" :-)
In fact, if such a GET parameter existed, I could remove the dialog and
replace it with a simple link. This sounds like a good idea in principle.
(It would also fix Leo Broukhis' issue.)
Does anyone kn
Haven't looked it over in detail, but here is the notice:
http://www.unece.org/fileadmin/DAM/cefact/locode/2015-2_UNLOCODE_SecretariatNotes.pdf
>From a quick scan: They've added latitude/longitude (to the minute, ~2km);
that's great because often the names of locations are ambiguous.
They still
If that's the only reason to post the form yourself, you could request the
addition of an optional get parameter on the adoption page. If it's clear
that this parameter is intended to be used by third party services the
"stability problem" would be solved.
Otherwise, great idea!
Thanks for the com
By "should end with the link" I implied "should not contain anything
that followed it at the time of my comment, including the form and
the - thus obviated - disclaimer. :)
If submitting a form to a 3rd party site results in an error for any
reason, the error will be displayed by the target host.
Thanks for the comment!
> As far as I'm concerned, the pop-up contents should end with the link
> "Read more about codepoint adoption." In your brief description, you
> might want to add a proviso about the temporary nature of character
> adoption.
Good catch! The 12-month period is important to m
As far as I'm concerned, the pop-up contents should end with the link
"Read more about codepoint adoption." In your brief description, you
might want to add a proviso about the temporary nature of character
adoption.
Submitting forms to a 3rd party site is a bad idea.
Leo
On Thu, Dec 17, 2015 a
Hi,
please let me start by saying, that I think the adoption of characters
is a very good idea to provide funding for the development of Unicode.
To promote this idea, I thought it could be worthwhile to place an
"adopt this codepoint" button on the description pages of code points on
https://cod
Good catch. Once again a lot of misconception by someone who wrote it
without looking at conformance requirements in these standards.
The so called "standard United States character set (437)" is also a
proprietary legacy charset widely used in the US but not adopted as an US
standard. It should ha
UN/LOCODE version 2015-2 has been released [1], and the Manual still
contains the following about character sets:
"27. Place names in UN/LOCODE are given in their national language
versions as expressed in the Roman alphabet using the 26 characters of
the character set adopted for international tr
9 matches
Mail list logo
