Welcome ;)
With the caveat that I'm not an i18n expert; what do you mean by
'different location'? IRIs don't have a separate level of %-encoding on
top of that used by URIs; rather, as I understand it, they leverage the
URI %-encoding mechanism, by just standardising on UTF-8 for the
character
At 11:10 05/04/12, Porges wrote:
OK, first-time poster :)
I was just thinking about IRIs recently and thought about a possible
source of ambiguousness. If the URI element can be EITHER an IRI or a
URI, then:
urihttp://example.com/200%25equalsZero/uri
This is both a valid IRI and a valid URI,
Thank you for the correction, Martin Dürst.
...I have a bit of a problem reading technical documents, my eyes tend
to glaze over a bit...
Please don't beat me too hard :)
On Apr 12, 2005 7:09 PM, Martin Duerst [EMAIL PROTECTED] wrote:
At 11:10 05/04/12, Porges wrote:
OK, first-time poster
At 7:58 PM +1200 4/12/05, Porges wrote:
...I have a bit of a problem reading technical documents, my eyes tend
to glaze over a bit...
Please don't beat me too hard :)
Note to everyone who feels the way Porges does:
At this point in the process, having implementers who are unfamiliar
with all the
I am not sure this is relevant but all this is supporting IRI?
jfc
At 13:24 31/01/2005, Bjoern Hoehrmann wrote:
* Robert Sayre wrote:
Suppose your user is subscribed to a feed containing 1000 entries. One
day, the host name is no longer capitalized. Are you going to put 1000
new, duplicate
