Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

French translation #85

Open
jejust opened this issue Aug 11, 2020 · 6 comments
Open

French translation #85

jejust opened this issue Aug 11, 2020 · 6 comments
Assignees
Labels
translation Enhancements related to translation

Comments

@jejust
Copy link
Contributor

jejust commented Aug 11, 2020

Hi all,
I love the idea of LearnLatex!
I'm starting a French translation. I have forked the main repository, and will send you a PR in a few days.

@davidcarlisle
Copy link
Member

Thanks.

You probably saw, but In case you missed it we have some general guidelines here
https://www.learnlatex.org/TRANSLATIONS

@davidcarlisle davidcarlisle added the translation Enhancements related to translation label Aug 11, 2020
@davidcarlisle
Copy link
Member

@jejust

I had a quick look at the fork and I notice spaces around punctuation in the French style eg

« Termes » :

I wonder if you have any thoughts on how to handle this in the markdown, there are I think three possible approaches

  1. You could globally edit the spaces to   (or similar for thin spaces)

  2. We could define variables in _config.yml like the existing variable for latex to make the LaTeX logo, something like

    thinsp: "<span style='white-space:nowrap'>&thinsp;</span>"
    

    so you would be able to use {{thinsp}} to get a non breaking thin space.

  3. Just leave normal spaces in the markdown but get Jekyll to do regular expression replaces to fix up the spacing, there is some suggested code here:

    https://www.sylvaindurand.org/improving-typography-on-jekyll/

    This option probably makes the most readable markdown source but I'm not sure if it adversely affects the time to build the site, we could try it though.

But maybe you have more experience of using gh-pages for French texts and have a better suggestion:-)

@jejust
Copy link
Contributor Author

jejust commented Aug 13, 2020

@davidcarlisle
Thank you for having a look at the French translation!

You're right, the spacing before ; : ! ? and » (and after «) is currently not correct, and even inconsistent from one sentence to the other because I didn't know what to do (I'm used to having LaTeX+Babel handle it for me... ;-).
I have absolutely no experience with Jekyll in any language, and I will evaluate your suggestions, that all seem valid. I will also seek advice around me, here in France.

For now, I've focused on the words, and it's almost done. I will send you a first PR tomorrow, hopefully, and then I'll have a few people read it to make the wording more idiomatic, decide if I want to translate the examples, and fix this spacing problem...

@davidcarlisle
Copy link
Member

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

@jejust
Copy link
Contributor Author

jejust commented Sep 24, 2020

just a note to say that we have extended lesson-06 and more-06 to add
descriptions of defining commands with \newcommand and \NewDocumentCommand

Translated, thanks!
Wouldn't it be worth mentioning \renewcommand? I can imagine a beginner will quickly try to redefine existing commands, on purpose or not.

@davidcarlisle
Copy link
Member

@jejust thanks, not mentioning the renew... was intentional although we may yet come back to that. There had always been some plan to mention definitions somewhere but what triggered us to add text now was yet another! question on tex.sx where something broke as a user had used \def and over-written a core latex command. Telling people to use \newcommand is one approach to that, if they just use \renewcommand instead it doesn't really help:-)

That said, while I wouldn't want to make an example using \renewcommand I did wonder about having an example that gave an error and describe in the text how using a different name or \renewcommand would solve the problem.
I think leave it for a bit see if this new section gets any other comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
translation Enhancements related to translation
Projects
None yet
Development

No branches or pull requests

2 participants