Re: Merging en & ja jlreq

> I can certainly make this happen, if the group doesn't disagree.

We’ll discuss at the next f2f meeting on 5/21 and come up with a consensus.

best,
- kida

> 2019/05/02 17:21、r12a <ishida@w3.org>のメール:
> 
> [cc+ Fuqiao for thoughts on whether this should be applied to the clreq doc too]
> 
> On 02/05/2019 03:11, Yasuo Kida wrote:
>> 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?
> 
> I can certainly make this happen, if the group doesn't disagree.
> 
> For now i'll wait for any further comments.  When there appears to be a consensus, let me know and i'll make any necessary changes.
> 
> (I may apply the same logic to the klreq editor's draft, in the meantime.)
> 
> ri
> 
> 
> 
>>> 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://w3c.github.io/jlreq/temporary_bilingual_devt/?lang=ja#chapter_2
>>> 
>>> 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
>>> 
>>> 
>

Received on Friday, 3 May 2019 00:33:37 UTC