Internationalization / add translations
Translate the interface of Gitlab
We’re accepting merge requests after the 6 points in the comment are addressed.
Björn Strausmann commented
Is the topic still current? I would like to take the translation into German.
But I can not ask for German at https://www.transifex.com/gitlab/gitlab/.
This is now moved to https://gitlab.com/gitlab-org/gitlab-ce/issues/4012
@Erwane: No this isn't the official transifex repository.
Gitlab doesn't support localization yet.
This is the official Transifex ? https://www.transifex.com/gitlab/gitlab/language/en/
Can you update English for v8.4 ?
will that be possible for gitlab to issue a collaboration model that allows 3rd party company like to us, to maintain and resell gitlab enterprise edition in local language, eg, Chinese?
We're not working on it now.
We still welcome any MRs and we're considering using Transifex after all.
Nikita Gryzlov commented
Any news about this feature?
My "bad English speaking" colleagues from the state-funded organization are looking forward to achieve this feature
Don't take my last comment. Didn't see the declined message was from past.
What the deal with Porus-P4? Is This functionnality available on Community Edition?
So starting a work about it is not interesting, isn't it?
We're emailing with Porus-P4 to get this implemented. We also need to be careful about performance and memory usage, see http://samsaffron.com/archive/2015/03/31/debugging-memory-leaks-in-ruby
Just see the declined message: "This will add a lot of friction when implementing new features."
I don't see the problem. Untranslated message will just be fallback on english message.
We just have to see a correct translation system to indicate translation progress, then contributors can fix them.
@123Haynes I'm very interessted to have this feature.
I could spend some time on it to make a proposition after this PR: https://github.com/gitlabhq/gitlabhq/pull/9055
KingJin no. Gitlab doesn't support internationalization yet.
https://www.transifex.com/projects/p/gitlab-1/ this is the official one?
I would like to translate English to Chinese, any place i could get the .po file.
I would translate from english to japanese.
"3: Need to check what is stored in databases that is not user supplied but generated, this text should be translated before being saved "
Wouldn't it be better to store the translation key in the db and translate it on reading in this case? So the user can switch languages without having to worry about what is stored in the database and what not.
Another quick question that I'd like to ask is with regards to how we intend on implementing the internationalization efforts of GitLab-EE, considering that source code is available only for the community edition.
We were trying to make a rough estimate of the work and scope needed to accomplish the task of translating the Gitlab site ( including all its finer details). Please feel free to add any feedback wherever applicable. Our aim is to determine what exactly within the site needs to get translated and how many resources we would need to allot for the task. Here is what we came up with:
Note that the numbers represent the effort towards the task where
0: Minimal effort
1: Half to one day worth of effort
2: Fairly large but straight-forward task, needs 2-3 days to complete
3: Fair level of complexity, may need further investigation into the task pieces
##### Translation Section Tasks
- 1: Setup en locale to have a special dates and times section
- 3: Determine all rails validation error message keys that need to be created
- 3: Setup special sections to support built in rails validation error messages
- 2: Determine all rails model keys that need to be created
- 2: Setup special sections to support rails model and model attributes display translations
- 3: Update all text and dates and times in app/views
- 3: Update all text and dates and times in app/controllers
- 2: Update all text and dates and times in app/finders
- 3: Update all text and dates and times in app/helpers
- 3: Update all text and dates and times in app/mailers
- 3: Update all text and dates and times in app/models
- 2: Update all text and dates and times in app/services
- 1: Update all text and dates and times in app/uploaders
- 1: Update all text and dates and times in app/workers
- 2: Examine extent of use of text in lib
- 3: Update all text and dates and times in lib
- 2: Need plan for static files in public such as 404
### Additional Tasks/Concerns
- 3: Need to check what is stored in databases that is not user supplied but generated, this text should be translated before being saved
- 3: Manual QA to ensure all strings are encoded, this task occurs mostly after the main effort is completed and is generally a manual process of using the site under a second language and making sure you don't see any English
1. Do we foresee us translating any upstream gems that are referenced within the application? If yes, then which ones, and are we aware of a strategy on how we might go about internationalizing those gems.
2. We have not included translation of currencies in our estimation. Are there any points in the application where currency translation might be needed?
3. Do we intend running automated tests in non-English languages. In that case, a large number of strings in the Rspec & Spinach tests would need to be changed, so that they may get referenced by the i18n translation system. Any take on that?
It would be great to have someone do a detailed review of our task list as we intend to use it in moving ahead with the internationalization effort. And, if we have missed any potential action items within our task list, or over/under estimated any, please do bring it up.
Thank you for the help. That was kind of you
I have a weblate instance ready.
I simply used the available bitnami stack to set it up.
Took about 5 minutes and wasn't complex at all :)
Please contact me at 123haynes [at] gmail [dot] com for the url and login details.