Target completion date: 01 Aug 2009
to support our translation effort!
If you want to participate in the overall project, add your name to the "*Participants*" field in the form.
Provide coordination,translations, and tools for the internationalisation effort. This includes
- (1) string translations covering core, system messages, templates, extensions and a few topics
- (2) wiki documentation covering installation process and all the other user documentations
- (3) evangelizing new translators for new languages (also look for projects which provide translations for open source projects, eg, ibiblio open source writer's group
- (4) find replacements for translators as they leave the project
- (5) influence UI design as required for translations
- (6) research, design, and implement a mechanism to provide translations for plugins
Suggested Plan for the task team
Set up a translation framework
For (1) a solution has to be built, which will extend the translation to existing extensions and will handle translation work on a proper webbased platform. Having extensions translated will generate a great impact on our translation effort.
Translate essential documentation
For (2) the documentation should first be written properly, before it got translated to 12+ languages.
Server access to install a web-based translation tool
It would be good to include the TranslationTaskTeam
in this team too, as they will have an influence on how documents are worded.
- 04 Nov 2008
I am not sure if a TranslationTaskTeam
will have influence on how the (original) documents are worded. But I think there have to be various steps that should be considered for documentation and, later on, the corresponding translations:
- Defining terms - and with that I refer to terms that for normal users are simple and easy to remember and still go straight to the point.
There were long discussions whether a page is a topic or a topic a page, but let's keep it simple: By the end of the day, the user will see a web page in his browser. So without wanting to start this discussion again, I believe that everything, that has to do with how to call the different elements of this wiki, should be defined once and after that never again.
- Having the terms defined and having them simple, the translation will be simple.
Staying with the example of topic and page: It is simple in English, but may be complicated in other languages because the difference between the word
page is semantically not necessarily the same.
- This done, all documentation must be revised and the terms must be substituted accordingly. I think this will be the first big task for this team. If the content of the documentation can be updated during the same step, even better.
- The updated version of the documentation has to be frozen so that translation can start. And yes, translation is very important to spread this wiki. Although english is standard for everything that has to do with IT, reading a manual in her/his own language is still the most comfortable. Besides, the administrator might be used to read documentation in english, but the end user definitively not.
- When changes on the core documentation are made, a mechanism has to be found so that updating the translations is easy. Presently, it is a p*** because one has to go through each line of the original document, make sure that the translation is still ok and figure out, where something changed (maybe just one sentence). And if it is a long document, good luck Version comparison is only of little help, because translations are not literal. So maybe what is standing at the beginning of a sentence in English, might be at the end of the sentence in Spanish or German.
- There should be a kind of index that indicates if an original core document has already been translated (or not) and to which languages, and if an update of the translated documents is required because the the core document was updated.
- Documents that have no translation should refer back to the original (English) document. But that's more a task for the TranslationTeam.
- 06 Nov 2008
[...] Has something like Google Translate been considered to assist in automating some of the translation? Probably it would not give a very polished translation, but the places it would have difficulty might be somewhat predictable, so that a second stage of processing could be done in Perl, followed by a final proof-reading by a human fluent in the language.
- 10 Nov 2008 - 10:53
Added myself, you already know why, now in order to help in the documentation translation I have to have some copy of the documentation in a special page in order to translate or whatever...
Special note: Can you separate pt-br from pt-pt on the translators list? In order to I add myself?
carlos, separated. please add yourself to the list as appropriate. the only reason it wasn't already separated was because we only had BR translations. i wonder when/if something will happen with the spanish translations? (the original, and i assume current ES translation should actually be ES_MX)
- 19 Nov 2008 - 22:16
Hey Will, in fact it should be ES_CR
I just seperated it, but at the same time, I started to doubt if it makes sense. Obviously, there are (important?) regional differences that affect the translation of a string. On the other hand, we will start sharing resources. If there were four translators for Spanish, suddenly there might be only one or two for a Spanish subgroup. So?
- 22 Nov 2008 - 18:36
Is there a particular place to discuss general translation problems? I'm working on the Swedish translation and would like some advice on how to translate the tagline, since I'd like to get that right from the start. The tagline "Free and Open Source Wiki" sounds great in English, but it might not translate easily into other languages. To point me in the right direction, could someone tell me if the word "free" is supposed to refer to the wiki or to the source. In other words, which of the following do you consider to have the same meaning as the tagline:
- "Foswiki is a free wiki that is based on open source"
- "Foswiki is a wiki that is based on free and open source"
I know it's a subtle difference, but hopefully someone knows what we want to communicate to potential users.
- 27 Dec 2008 - 13:53
Kan man inte säger: "Foswiki - det frit och öppet source wiki"?
I think every language will have some speciality in it. Yesterday we talked about if Foswiki is male or female
I like your suggestion to have a special page where we define a bit more the character of Foswiki and build up a common sense. This also could give orientation for new translations and translators.
- 27 Dec 2008 - 19:27
Great, I see that you know some Swedish. Your suggestion isn't entirely gramatically correct, however. The phrase "free and open source" translates to "fri och öppen källkod", but it's impossible to cram the word "wiki" into the phrase in Swedish. I'm not a grammar expert, but it probably has to do with the fact that "open source" is used as an adjective in English without actually being an adjective. For now I'll settle for the translation "den fria wikin baserad på öppen källkod" which conveys both that the wiki (i.e. the software) is free and that its source is open.
- 27 Dec 2008 - 20:36
Formal or Informal Language?
Do we use formal or informal language? Is there already some agreement about that in the community? I propose keeping the formal languages as minimum standard for the releases of foswiki, but to use informal language in the international webs on foswiki.org.
- 09 Jan 2009
Have you ever thought about putting Foswiki to BetaWiki
- 26 Jan 2009
Fully translated templates as an Internationalisation alternative approach
About the translation system I have found some issues I would like to discuss
- The use of MAKETEXT is OK when we want an international site with many languages. But in most corporate contexts this is not the case. Intranets are almost always in a single local language, so the constant use of the translation function is a performance loss with no benefits at all. If Foswiki is supposed to be oriented to enterprise environment an alternative way of translation should be provided.
- I think fully translated templates can be a better choice in the case the use of only one language is needed. The multi-language options must exist too but this option of only one language is also necessary. A way to achieve this can be the development of a script to replace MAKETEXT functions in the templates using the information in the .po files.
- In TWiki If I need a single language Intranet I have to modify the templates to remove the language bar. This could be fixed in Foswiki defining it from configure script. Maybe just defining only one language in locales options the bar is removed. That case English should not be forced if it is no needed.
I have used fully translated templates in two Spanish language Intranets with good results for two years so I think both translation approaches should be provided in the site to be downloaded with every version. I would also be glad to collaborate in this effort.
- 17 Feb 2009
This sounds like a good idea. The fully translated templates could be organized in subfolders, one folder per langauge.
The interface translation is just one aspect of I8N
. What about the content? Do you have ideas for the proper organization/structure of a Wiki site with content in multiple languages? How would we do this using Foswiki?
- 17 Feb 2009
No, I have no too much experience working with multi language environments. Besides I have not seen too much effort put on the translation of the content. In current .po files the translated context is minimal. In the sites I have used in Spanish I have found almost mandatory to translate the welcome page, the tutorials and the help pages. I had to translate also all the topics of the _default web.
I think the rest of the default content is mostly administrative, so the ability to read it could be included in the AdminSkillsAssumptions
- 19 Feb 2009
Question from the association board
- is the work of this task team now complete? The target completion date has been passed. If not, you may want to revisit your goals. BTW I changed your status to "running" as you have been de facto for a long time now.
Andre, can we have a status update please?
- 09 Dec 2009
Hi, I am new user, we will start using FosWiki
at our organisation. I started to Turkish translations. I am planning to finish translation of mostly used parts at the end of april. I registered at translate.foswiki.org with username yamant. How can i add Turkish Language to translate.foswiki.org ?
- 06 Apr 2010
that's great news! thanks! i've created Tasks.Item8854
to work on this and started the process.
- 07 Apr 2010
Hey out there.
Just wanted to see if there are some news here. Things seem a little stuck what translations is concerned
Maybe someone can shed some light in here: Are we still working with the *.po files. Or only with the pottle server? From the programmers' side, are the *.po files enough or is also translation of core documentation intended / required? If it is, how will this implementation take place? In seperate webs for each language. Or some big MAKETEXT chunks?
Thanks in advance!
- 11 May 2010
We are working with *.po files and this will also be the case for strings inside code for the future. On top users can translate via our Translation-Server: http://translate.foswiki.org
A translation of all documentation is not planned yet. The original documentation has to be streamlined in advanced, before it will be translated into 20 languages. IMHO 3 documents which cover the most central aspects would be enough for the start.
- 14 Sep 2010
The information around translating Foswiki is heavily outdated. For instance, TranslationUserInterface
doesn't even mention translate.foswiki.org.
Could you as a team create a better entry point for new translators?
- 14 Oct 2012
This team is in need of a new team lead as Andre hasn't been seen on the project for a long time. Andre, are you still available? Or anybody else on the list: please step forward to take the lead. Thanks.
- 22 May 2013