Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update links to BCP 47 #324

Closed
wants to merge 1 commit into from
Closed

Update links to BCP 47 #324

wants to merge 1 commit into from

Conversation

xfq
Copy link
Member

@xfq xfq commented Nov 18, 2021

Fix #321

@r12a
Copy link
Contributor

r12a commented Nov 18, 2021

I see that you're using links like https://tools.ietf.org/search/bcp47#section-2.2.7 rather than https://www.rfc-editor.org/rfc/rfc5646.html#section-2.2.7. Do you think that's better?

@xfq
Copy link
Member Author

xfq commented Nov 18, 2021

I think these two links are similar to https://www.w3.org/TR/jlreq/ and https://www.w3.org/TR/2020/NOTE-jlreq-20200811/

The first one always links to the latest version of the IETF language tag standard, and the second one may be obsoleted by another RFC document. For those who want to link to a stable version, the latter is better, and for those who want to always point to the latest version, the former is better.

Another difference is that BCP 47 contains two RFC documents. I linked to BCP 47 here because specdev recommends linking to BCP 47.

@r12a r12a self-requested a review November 18, 2021 12:43
@xfq xfq added the DONT MERGE label Nov 23, 2021
@xfq
Copy link
Member Author

xfq commented Nov 23, 2021

(Before merging this, I will discuss this issue with the i18n WG first.)

@xfq
Copy link
Member Author

xfq commented Dec 3, 2021

Closing in favor of #329

@xfq xfq closed this Dec 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

404 for http://tools.ietf.org/html/bcp47
2 participants