Opened 17 years ago
Closed 15 years ago
#6387 closed defect (fixed)
docs about translation
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | high | Milestone: | 0.12 |
Component: | i18n | Version: | 0.12dev |
Severity: | normal | Keywords: | documentation i18n |
Cc: | trac@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
would be nice to have a wiki article which describes, how/where to add translation files (e.g. de_DE) for interface translation
See TracL10N.
Attachments (1)
Change History (23)
comment:1 by , 17 years ago
comment:3 by , 17 years ago
i need to know, where to put the translated *.po files and how configure trac to use them.. im not interessted in the system how the i18n is implemented.
comment:5 by , 17 years ago
Keywords: | documentation i18n added |
---|---|
Milestone: | → 0.12 |
Owner: | changed from | to
jruigrok:
cboos:
Btw, is there a dev page describing how to use this i18n branch (generate the catalogs and such)?
I thought there was, but now I am in doubt. Need to check it and if it does not exist I should create it.
Anyway:
get Babel all installed
then from the trac-i18n branch:
python setup.py —help-commands
extract_messages is for creating the .pot
compile_catalog is for creating .mo files from .po files
after that build and install to test .mo files
I hope this gets you a bit further ;-)
comment:9 by , 17 years ago
its very confusing that the term L10N is used, even if we talk about I18N …
comment:10 by , 17 years ago
Component: | general → i18n |
---|
comment:11 by , 17 years ago
A quick note: L10N is actually quite correct for the translations, since it is the localization of the software. I18N would be less appropriate since that's the framework on the software side that makes L10N an option.
comment:12 by , 17 years ago
I don't think so… if you talk about I18N you talk about translations and if you talk about L10N you talk about contents which you serve for a special region
comment:13 by , 17 years ago
In what time sandbox/i18n/trac/locale/messages.pot have regenerated
what i meen?
i've download the latest Babel-1.0dev_r358 and in Trac said
./setup.py extract_messages
my workcopy of i18n At revision 6706.
then i said
svn status ? trac/locale/es_AR/LC_MESSAGES/messages.mo M trac/locale/messages.pot
i dont now, may be it not need, but i will atached the patch for trac/locale/messages.pot
comment:14 by , 17 years ago
not in messages.pot
#: web/auth.py:89 #, python-format msgid "logged in %s" msgstr ""
maybe create new ticket for this type of messages?
comment:15 by , 16 years ago
Milestone: | 0.13 → 0.12 |
---|
comment:16 by , 16 years ago
This desperately needs some docs. I've installed 0.12 and the "language" panel on the preferences shows up, but changing it does nothing. I have no idea what I'm missing or where to start.
comment:17 by , 16 years ago
Owner: | changed from | to
---|---|
Priority: | normal → highest |
Status: | assigned → new |
Version: | → 0.12dev |
#7843 closed as duplicate - asking for some more precisions about the installation of .mo files.
follow-up: 19 comment:18 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Replying to markus.staab@…:
would be nice to have a wiki article which describes, how/where to add translation files (e.g. de_DE) for interface translation
We are working on that. Hope we will have it in production until the end of year.
comment:19 by , 16 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Replying to anonymous:
Replying to markus.staab@…:
would be nice to have a wiki article which describes, how/where to add translation files (e.g. de_DE) for interface translation
We are working on that. Hope we will have it in production until the end of year.
Please do not close this ticket. It's highly important to me to have a resolution as soon as possible.
comment:21 by , 15 years ago
Priority: | highest → high |
---|---|
Type: | task → defect |
follow-up: 23 comment:22 by , 15 years ago
Summary: | docs about translation → doc about translating plugins |
---|
Focus the ticket on expanding TracL10N for adding translation support to plugins.
The TracMercurial plugin has translations, so it's already possible to do it by following that example, but a few more guidelines wouldn't hurt…
comment:23 by , 15 years ago
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | reopened → closed |
Summary: | doc about translating plugins → docs about translation |
Replying to cboos:
Focus the ticket on expanding TracL10N for adding translation support to plugins.
Oops, there was already a ticket dedicated to this (#6387), so this ticket is about the general documentation for translation, which is there in TracL10N and is enough. Improvements can be contributed directly by editing that wiki page.
Please see TracL10N for now. I need to substantially clean that up though, but it should help you a bit already.