Opened 8 years ago

Last modified 8 years ago

#117 assigned defect

conformance requirements in bidi document -- do they belong?

Reported by: masinter@… Owned by: adil@…
Priority: major Milestone:
Component: bidi-guidelines Version:
Severity: - Keywords: bidi
Cc:

Description

The document says "Bidirectional IRIs MUST be rendered by using the Unicode Bidi IRIs MUST be visually ordered by the Unicode Bidirectional Bidirectional Algorithm [UNIV6], [UNI9]."

There was significant discussion on the working group mailing list that this advice should not be normative. If it is normative, it isn't clear about to whom it applies -- who must do what kind of rendering? And if you just leave off the "http://" in the first place, is what you're rendering an IRI or something else?

What is the consequence of not following this bit of advice anyway?

Change History (3)

comment:1 Changed 8 years ago by duerst@…

Larry writes:

The document says "Bidirectional IRIs MUST be rendered by using the Unicode Bidi IRIs MUST be visually ordered by the Unicode Bidirectional Bidirectional Algorithm [UNIV6], [UNI9]."

This isn't the relevant bit of text, because rendering by the Bidi algorithm isn't the issue, it's what context or additional tweaks should be allowed (or not)

There was significant discussion on the working group mailing list that this advice should not be normative.

It's not about being normative or not. It's about whether another way of rendering, or several ways of rendering, should be allowed.

What is the consequence of not following this bit of advice anyway?

The consequence is that bidi IRIs get garbled; components get moved around, and users get confused. Maybe to some extent unavoidable, but definitely not a good thing.

comment:2 Changed 8 years ago by adil@…

  • Keywords bidi added
  • Owner changed from draft-ietf-iri-3987bis@… to adil@…
  • Status changed from new to assigned

comment:3 Changed 8 years ago by adil@…

  • Component changed from 3987bis to bidi-guidelines
Note: See TracTickets for help on using tickets.