Merging en & ja jlreq

I see that there is interest in merging the languages into a single 
document, as we did for clreq (https://w3c.github.io/clreq/) and klreq 
(https://w3c.github.io/klreq/).

I though i should mention that such an approach has its own set of 
complexities when it comes to editing and maintaining the document. 
There are classes available to indicate when one language is out of 
synch with another, and to allow a reader to view in one language or the 
other, but they are a little fiddly to manage.

I don't remember the details of the discussion, but i do seem to 
remember that we did take a decision to separate the documents when i 
ported jlreq to GH, because we thought it would make life simpler.  If 
only because it's a LOT of work to merge the two docs.

Just thought i should mention that, to contribute to the discussion.

cheers,
ri


On 15/04/2019 10:02, Atsushi Shimono (W3C Team) wrote:
> On 2019/04/15 04:48, Yasuo Kida wrote:
>> *JLReq TF **議事録、日本語版*
>> 2019 March 12th
> 
>> *議事録*
>>
>>   * JLReq アップデート


>>       o *日本語と英語のページを統合する**: * 下農さんが、現在別々のURL 
>> にある日本語と英語のページを統合することを提案。他の言語と一貫した形式 
>> になること、メンテナンスが簡単になることが利点。合意。統合したページを 
>> 作る には、現在の公開されているページではなく、日本語と英語が併記して 
>> あるソースドキュメントから始めるのがより簡単。一旦統合ページができれ 
>> ば、以降の アップデートはその統合ページの上で行うことができる。
> 
> 
>>> *Minutes*
>>>
>>>   * JLReq updates


>>>       o *Merging J&E html*: Shimono-San proposed to merge the English 
>>> and Japanese html to make maintenance easier and to make it 
>>> consistent with other languages. agreed. It is easier to come up with 
>>> the merged html from the original document which has Japanese and 
>>> English in parallel already. Once the merged html is created future 
>>> updates will be done on this file.

Received on Monday, 15 April 2019 15:16:30 UTC