@SachaWiedmaier, let’s make a thread with your questions.
I could show you around the little I know about github/pyRevit
I won’t go too much indepth as @eirannejad might have a broader way of making the translation happen (@eirannejad feel free to edit my post)
One way of doing it:
-
make sure you have pyRevit CLI installed (in command line type:
pyrevit env) -
setup github account here Sign in to GitHub · GitHub
-
download github desktop https://desktop.github.com/ you might want to use it to push your improvements to the pyRevit github repo
-
from the pyrevit repo page
-
then in the command line
pyrevit clones add main C:\pyRevit\mainto add your clone to pyRevit config file
C:\pyRevit\main being where I put my copy of the repo @ step 4 -
using the CLI command
pyrevit clonesyou should see your repo clone listed
-
you will want to use this clone for your test by attaching it to Revit
in the command line:pyrevit attach main 2711 --installed --allusers -
the pyRevit showing in your Revit should be the new clone now.
-
you can now edit the yaml files the do the translation. translate the pushbutton bundles like discussed earlier
fr_fr: Contrôle qualité en_us: Quality control tooltip: fr_fr: Permet de collecter les données importantes du projet pour le modèle courant et les modèles liés en_us: Collect key data from the current model and its links
“string” might be needed around the accentuated sentences
- to see it in action, save the yaml’s and then use the reload button in pyRevit but make sure to change the languages in the settings of pyRevit if you need to see your changes in different languages
- once you are happy with your changes, you can open github desktop and it will guide you to publish your changes
it will list you the changes
-
you can then commit them like so
-
once commited, you can push to the pyrevit repo but not directly, you need to create your own fork
-
confirm
-
you might have to push the commit again but to your fork now. anyway, a couple of clicks later your change has been send to your fork of pyRevit Repo
-
you should see this in your repositories on github
-
time to create your pull request (PR) to tell the pyRevit master you contributed to its efforts by translating some buttons:
- put a title and a description and then create it
Then you are done
you done need to do this one file at a time.
make the translations and once satisfied push them in batch
4 Likes
This is so great. Thanks @Jean-Marc!!
2 Likes
This is just that total great awesome answer for me to get it done easily !
Thank’s !! 
2 Likes
Translation in French for the tools of the UI done
@eirannejad 209 bundle.yaml files! That took quite a bit.
1 Like
For anyone interested, the french translation of the Settings: Settings translated in french by jmcouffin · Pull Request #1849 · eirannejad/pyRevit · GitHub
Anyone could add its own version. Quite tedious, especially with special characters
Russian version was done previously by @dosymep sanzoghenzo 
, I just followed
1 Like
The real hero here is @dosymep !
I might follow up with italian translation (no promises here 
)
2 Likes
Indeed @sanzoghenzo
I got a bit mixed up 
Hey @Jean-Marc , i want to add problem i encounter during the setup.
At the step 7 i got an error on which my CLI didnt find the engine 277. So to solve it, i had to run
pyrevit attach main 277 --installed --allusers --debug
At the end it will list all available engine like this.
As you can see i end up using the engine IPY340PR and was able to continue. You can check it by running
pyrevit env
Yes, the thread is old.
Instead or 277 you could have used DEFAULT or 2711
I edited the original thread
Thanks