Replies: 1 comment
-
|
I can start implementation if you like the idea. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
First of all great plugin, I love using it.
Second:
I want to introduce internationalization to various plugins, more specifically in the UI area.
Story
As I was studying japanese I wanted to translate my own dotfiles which I did succesfuly, but many other people used my setup as well so I added internationalization in my own dotfile. But as I was studying japanese I saw many people who used neovim which couldnt fully understand english. So this gave me the idea and resolution to go to the plugins and add internationalization capabilities.
Benefits:
Approach
My approach is as follows
To get the language set I am using a variable build in which Is
Once I get the language it changes the values depending on the languages available and translations.
For me I used a function that when text goes inside It tries to look for an available translation. if it doesnt have then it returns default string.
To load translation I developed this:
But to make all the PO's I made this cmake code
If you are interested I will like to implement this here. Not everyone who uses neovim is proficient in english, and I want to make it possible for everyone to enjoy the popular plugins in their own language, including this one. I know english and spanish, and I know some level of japanese to translate a good amount of stuff.
Here is a preview.
This is a preview of it working. the lualine and telescope I managed to grab their texts to replace them with what I wanted.
For example the telescope one looks like this.
it made two PO
which the japanese one looks as follows,
Beta Was this translation helpful? Give feedback.
All reactions