Language packs and requests
March 21st, 2007 by mira
There have been considerable number of queries mailed to us about various language packs for vtiger. Few of these are requests to bring out new language packs, while others are information seeking mails about existing language packs. Interestingly, we also receive mails from those interested in participating in various translation projects. In such cases, we refer them to the respective language pack maintainers, or encourage them to start their own translation projects at the forge. We have a good responsibility to help vtiger spread in many other countries & languages,as it has been doing now, particularly the past few months. The WiKi stores all information about the language packs and its respective maintainers for quick reference. In case there are any changes in your contact details, please keep us posted, we can keep that updated too. Also, please keep us posted about your latest packs, we could upload these in the website.
Help others find this article: 
|
|
|
|
|
Posted in General | | Post Comment | Permalink | Trackback
http://forums.vtiger.com/viewtopic.php?t=12506
This should be part of vtiger, it works pretty good.
and you can make your own lang pack in minutes.
Yes, I recollect seeing a good number of votes for that forum post!
Not at all. I find problems about encoding with this tool, unrevenged me… I’m language pack maintainer… T
You are package maintainer it’s seems that you are aware with open source philosophy then why dont post on the project bug in the forge ??
You take me for David Copperfield ? Or even better you can make a patch …
My reasons are simply.
1. Project activity Percentile: 21.62%, last
release was August 22, 2006. So, tool isn’t
available for latest vTiger version!
2. My priority is debuged core produkt. When we have
hardcoded strings that tool is unusable…
4. I dont know whether will be taken into core
product.
4. That tool don’t give me any amazing profit.
Save your time than speaking with me about open source philosophy, please. Kindly search for my name at trac, forge, forum.
It seems on the forum that people are using it successfully, assumingly with the latest release, but some of them have problems getting started. Let’s get some more people testing & using it, and get it out of beta!
Those who, like me, found the barrier to starting a translation on their own too high could get some contribution work done if there had been a friendly translation module available. I’m currently reviewing a lang.pack provided by one braver translator, who (hopefully) collected all the relevant files in some zip archives.
I’m sure a wizard is recommendable, also because some clients have their own ideas of what should be called what.
For translators it could also pay off with a default subversion package to get started translating with version control.
OK, im get it out for debuging after 5.0.3. release…
Another story. Lang pack version control would be much more easier if new labels will carry the hod at the file bottom. With notes like “added for xy version”. Not somewhere in middle…
This method was be used for 4.x series, but not ever in 5.x series. I dont know why. Mabe team have answer for us ?
Sure, we can solve this with serching for changes with some tool, but this eat time and may caused mistakes, needlessly.
I actually made it a point to tell the team to state specifically for which version the changes are being made. I will cross-check.
Mira: I think the lang pack wizard needs a special blog. Kindly bring it to the forefront.
Yes, that must be approriate. While my intention is to encourage the new translators on the block and provide them with any information required, the discussion drifted away into the specifics of the Langpack wizard!Let me put it as a separate topic for discussion, please. Thank you.