On Wednesday 19 September 2018 02:21:18 fredvs wrote:
> Not sure that using LyX will be easier than editing the pdf with
> LibreOffice Draw.and re-export as pdf.
> But ok, I will try with LyX.
Translating the LyX source is better because the document layout is defined
there. Simply modifying the output PDF can overlap other text and images as
the examples show. And if one changes the layout in LyX document all the
translation work is lost...
Please use for every language a separate git branch. Or does LaTeX-LyX provide
a better translation mechanism? I don't know LaTeX-LyX much.
>> I don't know LaTeX-LyX much.
> Huh, it is my first shot with LyX...
>> Please use for every language
> Saving as progpass_fr.lyx is not enough ?
No, because other files are language specific too, (source, LyX modules,
images...). It must be version tracked anyway.
I made the necessary branches and pushed them to gitlab:
In MSEgit you can click in the 'C' column (= checkout) of the branches
window in order to switch the language, see attachment.
BTW, it is spelled "Programmierspass" (Spass = fun).
Ok, it was in mse.module ---> mse_fr.module created.
> No, because other files are language specific too, (source, LyX modules,
Indeed, to do something nice, all the code of the examples should be updated
by language (hum, lot of work).
Why not use for all code-stuff exclusively English words? AFAIK, all
instruction/words in Pascal are in English too.
And in the pdf_lang give the translation of the English words used in the
demos an images.
On Wednesday 19 September 2018 20:13:31 fredvs wrote:
> Hello Martin.
> Ok, it was in mse.module ---> mse_fr.module created.
Please make the change in the dedicated branch, don't change the filename. So
later changes in mse.module can be propagated to the different languages
easily. An additional "mse_lang.module" which contains the language specific
expressions and which will be linked into "mse.module" probably would make
> > No, because other files are language specific too, (source, LyX modules,
> > images...).
> Indeed, to do something nice, all the code of the examples should be
> updated by language (hum, lot of work).
> Why not use for all code-stuff exclusively English words? AFAIK, all
> instruction/words in Pascal are in English too.
> And in the pdf_lang give the translation of the English words used in the
> demos an images.
It is because of the intended audience of German speaking pupils.
There was zero reaction of German speaking teachers so you are right, the
examples could be made in English.
On Thursday 20 September 2018 13:19:07 fredvs wrote:
> Hello Martin.
> Because of my terror of git, I will give the translated files in a zip file
> per lang.
> According your wishes. (no change in filename of the lyx file.)
Please post them to MSEuniverse. That there will be no common git history
which could be used to manage changes, improvements and extensions is bad.
But it is you choice of course.
On Thursday 20 September 2018 14:18:24 fredvs wrote:
> > Please post them to MSEuniverse.
> Brrrrr. They ask me for keys (and, like for my car, I do not know where
> they are).
It is like in GitHub.
- Copy from /mse_progfun/layouts, mse_en.module + mse_fr.module into your
- In LyX do Tools-Recompile.
- Edit progfun_en.lyx and change this lines according where you did save
On Friday 21 September 2018 00:06:29 fredvs wrote:
> > the examples could be made in English.
> And maybe the images too.
I know that I can not convince you, the following comments are meant for other
> I am not convinced that using branches would make things easier for the
> In my case, I load 2 projects in LyX, the template progfun_en.lyx and the
> target progfun_fr.lyx and compile + switch from one to the other.
> But if you work with git-branches it is much more complicated.
One would make two clones of the "book" repo in different directories so one
can work with two different branches at the same time.
> Also, each time you load the project with a other language, you have to
> paste the correspondent mse.module in /usr/share/lyx/layouts.
> And re-compile LyX.
One would use the local module in "book" repo instead.