Re: Merging en & ja jlreq

> I do think it is a bit weird for the English version to be authoritative, given the authors and the subject matter are Japanese. I would have thought to make the native language authoritative and the English translation be the reference.


ah, it is an interesting point. It is just my guess but W3C procedures mandate official documents to be English? In reality if there are conflicts between two documents probably almost always the one in Japanese is correct as it is the original work.

- kida

> 2019/05/02 11:28、Nat McCully <nmccully@adobe.com>のメール:
> 
> I am fine with non-automatic selection. I do think it is a bit weird for the English version to be authoritative, given the authors and the subject matter are Japanese. I would have thought to make the native language authoritative and the English translation be the reference.
> 
> ”ŖNat
>  
> From: Yasuo Kida <kida@mac.com>
> Sent: Wednesday, May 1, 2019 7:12 PM
> To: r12a
> Cc: public-jlreq-admin@w3.org
> Subject: Re: Merging en & ja jlreq
>  
> Thank you! If not automatic, I think it is the best to make English by default as opposed to show all, and optionally it is great if it accepts the lang parameter like you offered. 
> 
> Showing both English and Japanese would not be a common use case. It would be useful only when one wants to check the translation. 
> 
> JLReq members, what do all think? 
> 
> - kida 
> 
> > 2019/05/02 2:07”¢r12a <ishida@w3.org>¤Ī„į©`„ė: 
> > 
> > On 01/05/2019 01:31, Yasuo Kida wrote: 
> >> Right now it opens with all languages visible. Is it possible to make it English by default (or better yet to choose the default language by looking at the language setting of the browser)? 
> > 
> > 
> > For now, i allow you to add ?lang=ja/en to the URL. We may be able to do something more clever later, but i don't think it will be easy to automatically derive the language from the browser preferences on github, since it doesn't allow control of http header information. 
> > 
> > Here's a link you can try: 
> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fjlreq%2Ftemporary_bilingual_devt%2F%3Flang%3Dja%23chapter_2&amp;data=02%7C01%7Cnmccully%40adobe.com%7C1a309a93f04944dca45308d6cea39326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636923599335525414&amp;sdata=Snt3ZKjSEsvri7lUFvhWLmTW3sZHGjAj161JeNVeYKM%3D&amp;reserved=0 
> > 
> > There is a bit of a delay, since it has to display the whole document then remove the non-japanese bits. This will probably be less noticeable when loading a Working Draft from the W3C site, since we won't need to run all the respec scripting. 
> > 
> > hth 
> > ri 
> > 
> > 
> 
>