Skip to content

IDNA: avoid defining valid domain string in terms of the parser #245

Description

@annevk

This is basically something we need to raise again with the IDNA folks as their document does not really address it. This used to be tracked by https://www.w3.org/Bugs/Public/show_bug.cgi?id=25334.

As part of fixing this we should make it clear they are at least ASCII case-insensitive.

Metadata

Metadata

Assignees

No one assigned

    Labels

    i18n-trackerGroup bringing to attention of Internationalization, or tracked by i18n but not needing response.topic: idnatopic: validationPertaining to the rules for URL writing and validity (as opposed to parsing)

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions