• View
• Edit
• History
• Print
• Backlinks

Internationalizations-Talk

Translation Portal

According to the Library of Congress the language code for Slovenian is "sl", not "si". RandyB August 13, 2010, at 11:43 PM

I think it may be of some use to have a central page devoted to translation (aimed to translators) - the present page is for i18n by users. the translation portal is a central hub for translators as starting point jdd Unfortunately, an anonymous contributor have deleted on march,16 the link to the localization page, so it have disappeared in space. It was intended to be the resource you are searching for. I think these two pages shall be merged somewhat. The same contributor also have made an energic cleaning of the Internationalization page and the pertinence of all that erasing shall be carefully checked.PRZ

The creation of a "localization" group is a very good idea (I'm too new here to take such decision :-), but I think keeping at least one page aimed to translators in the PmWiki group is a good idea, must simpler to find, I guess. the other translator pages should be moved to the new group. jdd

As suggested by PRZ above and agreed by Petko (see Localization.Localization-Talk), the help for translators will be moved to the Localization group; while keeping the installation, configuration and usage of other language(s) support in the PmWiki documentation. But I have improved the introduction of the Internationalizations page, to take care of your concern that this information is not "easy to find". -- SchreyP April 04, 2010, at 06:38 AM

Multilingual pmWiki-based website, is it possible?

Would it be possible to set pmwiki in a way that allows to maintain a multilingual website? I realize when you discuss i10n and l18n you refer to the wiki system itself, but on the content level it may be more than desirable, especially if the user may select his/her desired language for the content. VirtualFlavius?

Might be possible and actually sort of a common feature. (A heavy-weight CMS I know offers several language instances of the same page "seamlessly" - which is different from the Wikipedia, where you have to actively change the Wikipedia instance.) Have you had a look at the PITS yet to see if someone already made a feature request for this? --Henning June 25, 2007, at 09:55 AM

I've had some success using (and extending) the SubgroupMarkup recipe for multilingual websites. This allows me to create different language instances of a page by appending a language code as a subgroup. For example, "Main/Homepage,EN" would refer to the English version of "Main/Homepage", "Main/Homepage,FR" would contain the French version, and so on. --gh? December 3, 2007

Is it possible to get ride of all accented letters in the distributed pmwiki files?

For example in the french translation, there is PmWikiFr.BacÀSable PmWikiFr.CréationAutomatiqueDeVignettes etc, it conflicts with some servers. --Farvardin

Hi. I agree with you, but I currently see no way other than manually (1) creating new pages without accented names, (2) moving the content and deleting the old pages, (3) fixing all links to point to the new pages. The French docs are on my non-urgent ToDo list, but I wouldn't mind if others could help out. --Petko May 08, 2009, at 05:19 AM

I've converted it to UTF-8, I couldn't get rid of the accented letters, but at least it will use utf-8. http://www.pmwiki.org/wiki/Cookbook/French --Farvardin