Japanese translation

[wtsnjp]

Following the instruction in TRANSLATIONS.md, I am happy to open this issue to announce that I have just started the Japanese translation. You can find the translation and its up-to-dated progress in the translation-ja branch of my folk.

Since the translation progress is too little for now (right now headings only), I haven't yet set up for the github-pages at this point. When I prepare a live test site so that to make people easily check for the translation, I will notify the URL in this thread. I hope this way works fine for you.

I am looking forward to working further with you 😄

[davidcarlisle]

Thanks a lot.

I should say that there are some Japanese examples already on the site, but they were just me checking that (u)platex was supported at the various back ends being used. Feel free to discard them when you get to those pages.

[wtsnjp]

I got it. I appreciate you and all the people involved to make (u)platex available on the backends.

[davidcarlisle]

Thank you for working on learnlatex.org translations.
You may have seen already if watching the repository but just a note
to say that we have extended lesson-06 and more-06 to add descriptions
of defining commands with \newcommand and \NewDocumentCommand

463d181

[davidcarlisle]

As you may have seen, the main site at learnlatex.org has been given a new design and some of the details of the language data have changed.

If you are still working on the translation, I have updated
https://www.learnlatex.org/TRANSLATIONS
to hopefully give correct instructions for the new layout, but if anything is not clear please ask

[wtsnjp]

Although the progress is slow, I am still working on this Japanese translation. Now I completed “literal” translation for all 16 main lessons (lesson-XX), and so started to host the demo site: https://wtsnjp.github.io/learnlatex.github.io/ja/

The content is still unsuitable for pLaTeX users, and that makes the translation too premature to be read by actual readers. I will continue working on further adjustment of explanations for pLaTeX and also the translation for other contents such as “More on this topic” (more-XX).

[davidcarlisle]

@wtsnjp Thanks for the status update.

Yes we'll need to leave it to you to a certain extent on how literal the translation needs to be. The "spirit" should be that it is the same course, translated, not a different course, but it also has to be useful to the readers...

At one extreme you could make it a Japanese language course on how to write English LaTeX documents, and leave all the platex specifics to language-xxx lessons at the end, but that might be too extreme.

If you switch the examples to Japanese using platex then you will naturally have to adjust the text in some places and use your judgement on how much to change the text.

You don't have to do the same for all examples: you can have some examples using pdftex and some in platex (or both) if you need to show the differences..

がんばろう！

(Hope that means something:-)

[davidcarlisle]

Oh I see you have translated the examples mostly. That's fine they should work at texlive.net and at Overleaf if you add

% !TeX platex

at the top of each. If you need fonts installing at TeXLive.net let me know we have a lot more space available than on my original aws trial host so adding new fonts is not a problem.

test

[wtsnjp]

Yes. I tested all of the examples with my local platex but have not yet tested with online systems. I noticed that I need to add the magic comments to the pLaTeX examples (most of all examples) and plan to do so.

Today I realize that there is a new "Setting" page on the website. Any possibility to change the default "Default Engine" to another engine from pdfLaTeX for a specific language?

[davidcarlisle]

Any possibility to change the default "Default Engine" to another engine from pdfLaTeX for a specific language?

I knew you were going to ask that:-)

Currently not really: the "settings page" is personal settings and disabled by default as uses cookies. but the default default is only set in one place in assets/scripts/runlatex.js

var rldefaultengine=getCookie('runlatex-engine');
if(rldefaultengine=="") rldefaultengine="pdflatex";

I'm not sure I want to make that variable (it complicates the site description a bit if you can't tell by looking which engine will be used) but I can see it might make the translations look nicer (@josephwright any thoughts??)

I think all you would need to do is change the above to

var rldefaultengine=getCookie('runlatex-engine');
if(rldefaultengine=="") {
 if(runlatex.defaultengine==null) {
   rldefaultengine="pdflatex";
 } else {
   rldefaultengine=runlatex.defaultengine;
}
}

Then put

runlatex.defaultengine="platex";

in ja/include/buttons.js

You could try that in your fork:-)

[davidcarlisle]

The code above doesn't work actually, the timing is wrong, but this simpler scheme works, you can put

var rldefaultengine=getCookie('runlatex-engine');
if(rldefaultengine=="") rldefaultengine="platex";

at the end of ja/buttons.js and that will work without changing runlatex.js at all.

You can try the examples here:

https://davidcarlisle.github.io/learnlatex.github.io/ja/help

The first has a !TeX comment and the second does not. Conversely I have added a %!TeX pdflatex comment to the English example on that page (although that simple case works with platex as well)

[wtsnjp]

Thank you very much for that! It is great because it can be all done within the "ja" subtree. I will definitely try it.

[davidcarlisle]

one reason having the comments may be simpler....

The above code makes it use platex unless the user has set a preference for something else, but that means if the user has (say) lualatex set as default for the rest of the site the ja pages will fail. It might be better not to look at the cookie and to just have unconditional

rldefaultengine="platex";

which would work the same way as having a platex comment on every page and use platex even if cookies have been set.

[wtsnjp]

The above code makes it use platex unless the user has set a preference for something else, but that means if the user has (say) lualatex set as default for the rest of the site the ja pages will fail.

Well, but if one set "default engine", then I feel it natural to fail running the examples, which are for platex, without explicit ! TEX comment. Isn't the user who set it by cookies responsible for that?

One small concern is that it still shows "pdfLaTeX" as the default engine in the option menu on ja/setting page, while the actual default engine is "pLaTeX" in this case.