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

Obtaining language from http headers #54

Closed
mattgarrish opened this issue Aug 28, 2017 · 5 comments
Closed

Obtaining language from http headers #54

mattgarrish opened this issue Aug 28, 2017 · 5 comments
Labels
i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. propose closing status:postponed topic:internationalization topic:manifest

Comments

@mattgarrish
Copy link
Member

A side-issue raised in #42 is whether http headers can be a fallback for obtaining the language of the publication.

Leaving for future discussion.

@BigBlueHat
Copy link
Member

Anyone interested in discussing this issue should give HTTP headers, meta elements and language information a good, thorough read.

It'd also be best to "zoom out" a bit and read through these articles also: https://www.w3.org/International/articlelist#language

We will be receiving review from this group prior to any final publication (re: Coordination in our charter).

@iherman
Copy link
Member

iherman commented Sep 2, 2017

We should postpone (and keep open) this issue until we get to the point where we discuss the overall role of HTTP (e.g., what is the HTTP response on the address of a publication, etc)

@dauwhe
Copy link
Contributor

dauwhe commented Jun 27, 2018

Is there any other answer besides "do what browsers do"?

@iherman
Copy link
Member

iherman commented Jun 27, 2018

No... :-)

The manifest does not give any information on the language of the content of the resources. The language must be established as the browsers do indeed...

@r12a r12a added the i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. label Jul 26, 2018
@wareid wareid added this to discuss - F2F in PWG Task Management Oct 10, 2018
@iherman
Copy link
Member

iherman commented Oct 23, 2018

This issue was discussed in a meeting.

  • RESOLVED: close #54
View the transcript Obtaining language from http headers #54
Tzviya Siegman: #54
Wendy Reid: Obtaining language from http headers (#54)
Wendy Reid: the issue is whether http headers can be fallback for determining the language of a publication
Tzviya Siegman: this is no longer relevant; it’s from a long time ago
Rachel Comerford: let’s add a comment saying this
Ivan Herman: I’ll clean the minutes then refer to them in a close comment
Resolution #5: close #54

@iherman iherman closed this as completed Oct 23, 2018
PWG Task Management automation moved this from discuss - F2F to Editorial Oct 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. propose closing status:postponed topic:internationalization topic:manifest
Projects
PWG Task Management
  
Editorial
Development

No branches or pull requests

5 participants