|
| |
| | Punycode - Wikipedia, the free encyclopedia |
 | | Punycode, defined in RFC 3492, is the self-proclaimed "bootstring encoding" of Unicode strings into the limited character set supported by the Domain Name System. | | | Note that for DNS use, the domain name string is assumed to have been normalized using Nameprep and (for top-level domains) filtered against an officially registered language table before being Punycoded, and that the DNS protocol sets limits on the acceptable lengths of the output Punycode string. | | | It is optimized for the case where the string is composed of zero or more ASCII characters and in addition characters from only one other script system, but will cope with any arbitrary Unicode string. |
|
http://en.wikipedia.org/wiki/Punycode
(1098 words)
|
|
| |
| | RFC 3492 |
| | Punycode is an instance of a more general algorithm called Bootstring, which allows strings composed from a small set of "basic" code points to uniquely represent any string of code points drawn from a larger set. | | | Punycode is a simple and efficient transfer encoding syntax designed for use with Internationalized Domain Names in Applications (IDNA). | | | Such ambiguities are usually resolved by context, but in a Punycode encoded string there is no context apparent to humans. |
|
http://www.apps.ietf.org/rfc/rfc3492.html
(6379 words)
|
|
| |
| | IDN Registrant FAQ |
| | Punycode is required because the restriction that only a subset of ASCII characters be used in URL/URI at the network protocol level is still enforced, even with the introduction of IDNs. | | | Punycode ("xn--"), was accepted as the IDNA standard by the Internet Assigned Numbers Authority (IANA) on 14 February 2003. | | | With a fully IDN-aware environment, you should be able to setup and use IDN for emails just as you would for ASCII only domains, using the Punycode form of the IDN. |
|
http://www.afilias.info/faqs/idn_registrant_faq
(2401 words)
|
|
| |
| | Watt-32 tcp/ip: SRC/PUNYCODE.H Source File |
| | The input is 00053 * represented as an array of ASCII code points, and the output 00054 * will be represented as an array of Unicode code points. | | | 00001 /* 00002 * punycode from RFC 3492 00003 * http://www.nicemice.net/idn/ 00004 * Adam M. Costello 00005 * http://www.nicemice.net/amc/ 00006 */ 00007 00008 #ifndef _w32_PUNYCODE_H 00009 #define _w32_PUNYCODE_H 00010 00011 enum punycode_status { 00012 punycode_success, 00013 punycode_bad_input, /* Input is invalid. | | | 00043 */ 00044 enum punycode_status punycode_encode (DWORD input_length, 00045 const DWORD *input, 00046 const BYTE *case_flags, 00047 size_t *output_length, 00048 char *output); 00049 00050 00051 /* 00052 * punycode_decode() converts Punycode to Unicode. |
|
http://www.bgnett.no/~giva/watt-doc/a01731.html
(634 words)
|
|
| |
| | Internationalized Domain Names (IDN) |
| | For example, the Punycode encoding of "südlich" is "xn--sdlich-3ya", and Punycode strings that are not identical to their inputs are prefixed with "xn--", so the IDNA domain name "südlich.example.com" would be represented as "xn--sdlich-3ya.example.com" in Punycode. | | | Punycode is specified by Network Working Group RFC 3492 | | | A list of unassigned code points is enumerated in table A.1 of RFC 3454 |
|
http://msdn.microsoft.com/library/en-us/intl/nls_IDN.asp
(1130 words)
|
|
| |
| | [No title] |
| | IDNA requires that implementations process input strings with Nameprep [NAMEPREP], which is a profile of Stringprep [STRINGPREP], and then with Punycode [PUNYCODE]. | | | Encode the sequence using the encoding algorithm in [PUNYCODE] and fail if there is an error. | | | Decode the sequence using the decoding algorithm in [PUNYCODE] and fail if there is an error. |
|
http://www.rfc-editor.org/rfc/rfc3490.txt
(6381 words)
|
|
| |
| | [No title] |
| | I believe the correct method for matching the CN with the HN+DN is to use the punycode version of the HN+DN. | | | The links are directed at "http://www.pаypal.com/", which the browsers punycode handlers render as www.xn--pypal-4ve.com. | | | Most browsers seem to match the punycode encoded hostname with the CN, yet a few (try to) match the raw UTF8 with the CN. |
|
http://www.shmoo.com/idn/homograph.txt
(986 words)
|
|
| |
| | Welcome to CAcert.org |
| | In short punycode is a way of encoding mutliple language characters in domain names without causing major changes in the way that domains work to accommodate this directly... | | | This is a valid concern in all browsers except Internet Explorer, and only because Microsoft had failed to implement any new major features in their browser of late. | | | See here for more details about this problem. |
|
http://www.cacert.org/news.php?from=rss&id=13
(253 words)
|
|
| |
| | SourceForge.net: wp-whois-proxy-devel |
| | I believe punycode is a light character encoding of unicode, but I"m not sure what the format is. The main effects on WP, as far as I can tell, will be the following: * ideally we shouldn"t strip punycode (but non-ascii) characters from query strings, so users can send punycode queries directly to us. | | | * in order to display the query string which was handed to us in punycode, we may need to do some contorting. | | | Verisign"s whois servers accept queries for IDN"s in "punycode" format. |
|
http://sourceforge.net/mailarchive/forum.php?thread_id=3648899&forum_id=35760
(186 words)
|
|
| |
| | Internationalized Domain Names (IDN) Support in Netscape 7.1/Mozilla 1.4 |
| | This is defined in RFC 3492 (Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)). | | | Since the Punycode contains only ASCII characters, it is possible that an output may, though unlikely, coincide with existing domain names. | | | This makes it possible for Netscape 7.1/Mozilla 1.4 users to access Japanese host names under.jp top domain without any additional setup using just the built-in IDN functionality. |
|
http://devedge-temp.mozilla.org/viewsource/2003/idn/index_en.html
(1529 words)
|
|
| |
| | WebNIC Premier Partner Program |
| | Therefore, a user must request registration information by initiating a WHOIS query for the domain name, in each language (native character set). | | | Therefore as partners/users, there is nothing need to be done by you. | | | As the protocol evolves, the beginning of the string (bq--) could change. |
|
http://www.webnic.cc/domainwholesale_domainfaq_idn.htm
(2519 words)
|
|
| |
| | Watt-32 tcp/ip: SRC/PUNYCODE.C Source File |
| | 00001 /* 00002 * punycode.c from RFC 3492 00003 * http://www.nicemice.net/idn/ 00004 * Adam M. Costello 00005 * http://www.nicemice.net/amc/ 00006 * 00007 * This is ANSI C code (C89) implementing Punycode (RFC 3492). |
|
http://www.bgnett.no/~giva/watt-doc/a01730.html
(500 words)
|
|
| |
| | Punycode Property, ByteArray class - Punycode conversion algorithm. Encoder and decoder. |
| | Punycode Property, ByteArray class - Punycode conversion algorithm. | | | Please use unicode code pages (utf-8 or utf-16, see ConvertCodePages) to work with all possible unicode characters. | | | Works with safearray binary data - save/restore binary data from/to a disk, convert to a string/hexstring, codepage/charset conversions, Base64 conversion, etc. |
|
http://www.motobit.com/help/scptutl/cm440.htm
(435 words)
|
|
| |
| | ICANN Letter from Rusty Lewis to Stuart Lynn (With Attachment Responding to IAB Statement) |
| | The Punycode version of the i-Nav plug-in will be delivered when the IDN RFCs have been published. | | | VGRS agrees with the IETF position that the IDNA, Nameprep, and Punycode RFCs should not address character variants. | | | VGRS will move to migrate its IDN systems to Punycode once the IDN standard has been published. |
|
http://www.icann.org/correspondence/lewis-letter-to-lynn-07feb03.htm
(2678 words)
|
|
| |
| | Re: [idn] Bulk UTF-8 / punycode Tool |
| | If you want to run it on a Windows machine, it can probably be built using Cygwin (but don't ask me how--I know nothing about Windows). | | | By the way, you need to consider whether you just want the Punycode encode operation, or the entire ToASCII operation (including Nameprep etc). | | | Georg Ochsner <[EMAIL PROTECTED]> wrote: > do you know an online tool or better windows programm yet to > automatically convert multiple strings containing german umlauts > (UTF-8) into punycode at once? |
|
http://www.mail-archive.com/idn@ops.ietf.org/msg04998.html
(168 words)
|
|
| |
| | New IDN Homograph Spoofing Response: IDN Will Not Be Disabled - MozillaZine Talkback |
| | Technically speaking, the Punycode version is the true domain name. | | | I would think the users who need these international character sets would have computers that show the international domain names correctly. | | | "I would also think they would prefer seeing the true domain names rather than 'Punycode'" |
|
http://www.mozillazine.org/talkback.html?article=6096
(1560 words)
|
|
| |
| | Docs for page Punycode.php |
| | The classes are based on documentation from RFC3454 (Stringprep), RFC3490 (IDNA), RFC3491 (Nameprep) and RFC3492 (Punycode). | | | All language-specific / national characters are encoded into what is known as "Punycode". | | | The Punycode comprises of "simple" ASCII-characters and therefor allows transparent use in DNS, webservers, mailers, proxies etc. All future browsers/email-clients are strongly encouraged to implement Punycode. |
|
http://pear.speedpartner.de/apidoc/I18N_Punycode/I18N_Punycode/_Punycode_Punycode_php.html
(104 words)
|
|
| |
| | [No title] |
| | punycode-decode string Function Returns a possibly multibyte string which is the decoding of the string which is a punycode encoded string. | | | punycode-encode string Function Returns a Punycode encoding of the string, after converting the input into UTF-8. | | | Data is read, line by line, from the standard input, and one of the operations indicated by command parameters are performed and the output is printed to standard output. |
|
http://www.dbnet.ece.ntua.gr/~adamo/howto/libidn.txt
(8894 words)
|
|
| |
| | [No title] |
| | In his blog post on Monday, Vishu Gupta of the Internet Explorer development team wrote about the use of Punycode to help make the internet more "international." By utilizing Punycode, Internet Explorer 7 intends to provide support for the International Domain Name (IDN) system. | | | As an extended security measure, Internet Explorer 7 features a built-in phishing filter, which compares a requested site against a list of sites that are known to be malicious. | | | Since Punycode allows for thousands of possible characters, Internet Explorer 7 implements security settings based on the browser's language configuration, which can be manually adjusted. |
|
http://arstechnica.com/journals/microsoft.ars/2005/12/20/2158
(568 words)
|
|
| |
| | DomainSite.com |
| | The problem with this is that users need a way to first have the native characters translated to Punycode before the domain will resolve. | | | Web browsers that currently perform the Unicode to Punycode translation are the latest versions of Mozilla, | | | You could register that domain in its Punycode form which is xn--online-9v7ik91d. |
|
http://www.domainsite.com/idn
(154 words)
|
|
| |
| | PCWorld.com - Next IE Beta Will See Global Domains |
| | Showing the punycode would all but eliminate spoofing but it's not user friendly, Gupta wrote. | | | The second beta release of Internet Explorer 7 will have support for URLs written in different languages, widely seen as critical for making the Internet more international, according to a Microsoft developer. | | | Punycode is an ASCII translation of Unicode domain names, the format allowed by the domain name system. |
|
http://www.pcworld.com/resource/article/0,aid,124056,pg,1,RSS,RSS,00.asp
(561 words)
|
|
| |
| | Public Interest Registry - Internationalized Domain Names |
| | The Domain Name System, which links text-based Web site names to numeric IP addresses and allows computers to locate Web sites, originally was limited largely to the characters used in English and the ASCII character set. | | | Punycode is a simple and efficient way of translating non-ASCII characters into a string of characters allowed in host name labels (ASCII letters, digits and hyphens) and back again. | | | Now, technical standards have been adopted to enable the registration of IDNs or domain names that are represented by native language, non-ASCII characters using Punycode. |
|
http://www.pir.org/GetAOrg/IDN.aspx
(261 words)
|
|
| |
| | Still At Large: Update on Response to Homograph Concerns |
| | The basis of IDN,is that every internationalized name exists in two formats, of which the one is displayed to the user in the full array of expected characters (Unicode), and the other is an encoded form (Punycode) that is only intelligible to purpose-designed software. | | | The initial design intent was for Punycode never to be revealed to users. | | | However, a number of situations where it is, in fact, beneficial for a user to see Punycode have become apparent in the interim. |
|
http://at-large.blogspot.com/2005/02/update-on-response-to-homograph.html
(388 words)
|
|
| |
| | [preannounce] Encode::Punycode |
| | AUTHOR Tatsuhiko Miyagawa This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. | | | Punycode is an efficient encoding (ACE) of Unicode for use with IDNA. | | | [1] http://www.ietf.org/internet-drafts/draft-ietf-idn-punycode-01.txt NAME Encode::Punycode - Encode plugin for Punycode encodings SYNOPSIS use Encode::Punycode; use Encode; $utf8 = decode('Punycode', $punycode); $punycode = encode('Punycode', $utf8); DESCRIPTION Encode::Punycode is an Encode plugin, which allows you to encode Unicode strings into Punycode. |
|
http://www.mhonarc.org/archive/html/perl-unicode/2002-05/msg00045.html
(132 words)
|
|
| |
| | PUNYCODE IDN Conversion for internationalized multilingual domain names |
| | Type the domain name or nameserver name that you would like to check in the input field. | | | To convert an IDN or nameserver from native characters or RACE to the Punycode version that is stored in the VeriSign Whois database: | | | This conversion tool will convert an International Domain Name (IDN) or nameserver from any one of the following formats to the others: |
|
http://webkor.com/multilingual_domain_race_conversion_sample.htm
(151 words)
|
|
| |
| | Repository - markup - cvs: libidn/lib/punycode.h |
| | If not punycode_success, then output_size and output might contain garbage. | | | Input arguments (to be supplied by the caller): input_length The number of ASCII code points in the input array. | | | Input arguments (to be supplied by the caller): input_length The number of code points in the input array and the number of flags in the case_flags array. |
|
http://josefsson.org/cgi-bin/viewcvs.cgi/libidn/lib/punycode.h?rev=1.11&view=auto
(977 words)
|
|
| |
| | ASP Punycode IDN decoder and encoder - Web Scripts Directory |
| | Description: Decoding and encoding between punycode, unicode string (BSTR), binary, utf-8 and conversion to/from other code pages. | | | On-line sample decoder and encoder of punycode data and IDN names. | | | Repeated votes and cheating the rating is not allowed and will result in a permanent 0 rating for this script. |
|
http://www.webscriptsdirectory.com/ASP/Networking-Tools/ASP-Punycode-IDN-decoder-and-encoder-L1531
(131 words)
|
|
| |
| | Rockliffe Support Contacts |
| | Any external software such as IDNNOW that deals with IDNs simply translates the IDN to and from Punycode. | | | It should be noted that for the IDNNOW plug-in to work in Outlook, Microsoft Word cannot be used to edit the e-mail. | | | test@tést.com, it comes through to the SMTPRA agent as a Punycode address ( |
|
http://www.rockliffe.com/support/docs/html/1/03/10318.asp
(625 words)
|
|
| |
| | Pandaura |
| | IE 7 may even incorporate a “phishing filter” where domains that IE 7 prevents as being viewed as Unicode will be checked against a list of known phishing sites. | | | In short, punycode is a standard of encoding international characters into Unicode strings that is supported by the Domain Name System. | | | The allowance of unicode scripts displayed in a users address bar depends on the user’s browser language settings. |
|
http://www.pandaura.com
(1937 words)
|
|
| |
| | dev-list.archive.0404: By Date |
| | HTTPS POST Authentication Error Fagyal, Csongor (Sat Apr 24 2004 - 09:49:35 EDT) | | | New IDN Punycode Questions John Keegan (Sun Apr 18 2004 - 21:51:30 EDT) | | | Re: New IDN Punycode Questions Sergei Kolodka (Mon Apr 19 2004 - 09:29:49 EDT) |
|
http://www.opensrs.org/archives/dev-list/0404/date.html
(300 words)
|
|
| |
| | Firefox Fixes Phishing Issue -
linking technology and productivity for Windows users |
| | Punycode is a subset of Unicode that is used when a part of a domain name can't be represented by ASCII characters. | | | You could also see phishers registering domains that use some of these similar characters. | | | You can see an example of this by visiting the Shmoo Group demo page. |
|
http://www.timeatlas.com/mos/The_News/Security/Firefox_Fixes_Phishing_Issue
(446 words)
|
|
| |
| | gemal.dk - IDN punycode display by top level domain |
| | More information in the bug report and in this document. | | | You're here: Home - IDN punycode display by top level domain | | | Mozilla Foundation products now only display IDNs in a whitelist of TLDs, which have policies stating what characters are permitted, and procedures for making sure that no homographic domains are registered to two different entities. |
|
http://gemal.dk/blog/2005/07/07/idn_punycode_display_by_top_level_domain?from=rss-category
(65 words)
|
|
| |
| | Re: [idn] AMC-ACE-Z has a name: Punycode |
| | ACE is what you get by applying ToASCII (which has several steps including Nameprep and Punycode). | | | The IDNA document uses the term ACE all over the place, but the references to Punycode and Nameprep are buried in the steps of ToASCII and ToUnicode. | | | tedd wrote: > Is "Punycode" really the name what you want to reflect the end-result > of this groups work effort? |
|
http://www.imc.org/idn/mail-archive/msg05348.html
(211 words)
|
|
| |
| | Punycode Converter |
| | This converter allows you to transfer domain names between the encoded (Punycode) notation and the decoded (UTF-8) notation. | | | Please feel free to report bugs and problems to: team@phlymail.de. | | | Just enter the domain name in the respective field and click on the button right below it to have it converted. |
|
http://idnaconv.phlymail.de
(129 words)
|
|
| |
| | WebMaster View: Firefox 1.0.1 (Security Update) |
| | International Domain Names are now displayed as punycode. | | | Syam Kumar February 25, 2005 07:36 PM Firefox 1.0.1 is released. |
|
http://www.webmasterview.com/browsers/firefox_101_security_update
(148 words)
|
|
| |
| | ICANNWatch Punycode IDN now active for .com and .net |
| | yggdrazil writes "I can't see that anyone has mentioned this, so I will: IDN domain names using the proper Punycode standard are now active in DNS!!! | | | Domain names previously registered with a BQ-- prefix is now active in the root zone for |
|
http://www.icannwatch.org/article.pl?sid=03/12/23/2238213&mode=thread
(908 words)
|
|
| |
| | ASPMessageboard.com |
| | To post in forums you must have an account - Create one now! | | | RE: internationalized domain names / punycode / ac |
|
http://www.aspmessageboard.com/forum/ASPPlus.asp?M=680122&P=1
(294 words)
|
|
|
