Joomla! Discussion Forums

Gave a helping hand and speeded up the updating. JED listing now have correct URLs 

That was quick - many thanks.

Hello.

Is it possible, to use this Language Manager to translate 3-rd part components and/or modules such as VirtueMart?
What should be done?
How tokens(?) are managed?

Regards.
T.

Yes and no.
Yes, if language file handling sticks to new Joomla! 1.5 localization file handling. No because, at this moment, VM doesn't.


Tak i nie.
Tak jeśli system plików językowych jest zgodny z nową architekturą lokalizacji w Joomla! 1.5. Nie bo w VM na razie nie jest.

I'm Vietnamese and I think that Joomla is so good with webmaster in VietNam. Vietnamese is required

Please contact our Vietnamese Translation Team
vhv_alex  http://forum.joomla.org/index.php?actio ... le;u=30421

Hi,

I've been watching this for a while and finally managed to download and install. This is such a great component! Kudos, Ifans!

Already done a bunch of translation files in basically no time, incl. a German translation of Translation Manager itself.
Feel free to add this to your distribution or do with it whatever you want. Its just the .ini files, and only a tiny, tiny contribution to your awesome work.
I have not yet managed to walk through all the many features

There's one "phrase" I coudn't find in your (en-GB) language file: "new key", the label used when adding a, well ... new key and phrase.

One dumb question though: where's the status of a file marked as complete stored? Is it just a session thing, or more permanent?

Thanks!

CirTap

Hi CirTap,

Thanks for the contribution and comments.  Have fixed the "New Key" and will update forge including your de-DE files soon.

The "complete" status works like this: when the checkbox is checked, the header of the INI file will include a tilde followed by the number of phrases which are the same in the source and translation files (e.g. ~2) in the translation INI file.  Each time the component parses the translation files, it checks this number for a match. If there have been changes in the source file (e.g. new or changed phrases) this match will usually be broken, so the status will no longer show as complete.

Regards

Ifan

Hi igevans,
just wanted to let you know it is a great component helping me a lot.

I wanted to ask if there's a plan for a Front-End part for this component, so I could share the translation process with other users without having to let them Administration access?



beside that, I think there is an alignment problem, but more on that when I have more time...

Same question goes for Access Level, at this point only Super-Admin can view the component, is the a config you can add to set a lower level (i.e Administrator)

I will need to combine a few versions of translation, any idea if the component will evolve in this direction any time soon? If not I will have to do some changes to the code to be able to do this.

I have, not very elegant, but efficient, idea on how to do this. There could be more directories starting wit locale with some suffix (eg. author nick) and then when opening an ini file component could go check on differences and display variants with a radiobutton to choose one which is going to endup in the main translation folder). It is heavy on resource, but then again I need it only for localhost.

If you are planing to provide solution to this and if I'll get it done my way, would you like to get the modification?
Would you have any questions / advices please feel free to contact me.

Is it the manager component that's has a problem with this line WHO\'S ONLINE=Who's Online or ? I've got the line in the translationpart and it also stands for deletion !?! Maybe there is a problem with the \ sign ?

OK, as Roman says, this could get complicated.

Personally, I want to avoid a database interface (for storing user rights etc) so am thinking about ways to get the required functionality.  A few questions:

USER/GROUP PERMISSIONS
---------------
This should be fairly straightforward, but not something I've done so far - any pointers greatly appreciated.

FRONTEND
---------------
I'm assuming I can "skin" the existing component from the forntend, without having to re-write everything. Will have a look over the enxt few days.

VERSIONING
----------------
This is the real challenge.  I agree that many files is probably the best way to do it, probably using the userID in the filename.  Questions:
* who decides which changes to accept?
* store unapplied changes or delete them?
* creation and deletion of phrases?
* using this method, there will be no way to display the unapplied changes in Joomla - any ideas on this?

TIMESCALE
-----------------
I have a new job, and so I haven't had much time on this hobby/project recently.  I would say probably 3-4 weeks to look at and implement the above.

[MOD note: offtopic messages regarding Language translation pack for Hindi and Gujrati split, and moved to: http://forum.joomla.org/index.php/topic,196835.0.html ]

Hi,
I'm getting an error only when showin translation files for the administrator:


I'm using: v1.5#7381

Is there a way to add an option to auto create the needed install.xml?

Is already there, just hit the 'Package' button in top menu of the component - and then download the package from the tmp folder (in the rot of your installation).

thanks, I never used that option, so I didn't know it really does that...

Hi

I'm discovering the TM and I'm absolutely amazed of this com_.

On little issue came to me while working on the french transl. : In the contact file, the word fax and information are exactly the same in french. Impossible to have the Unchanged Phrase mark removed !! How can I changed that so I can have a completed file status Am I clear

Thanks

Maximil

If I remember correct now the option for this is shown to you when you open a file for translation, theres a check box for 'Mark this translation as completed' (or similar). 

You're right but the counted strings still shows 32/34.

It's not a big issue and I won't fight for this, but i just wanted to inform about this ...

Maximil

That's a different thing - it's marked as ready anyway, right ... 

Thanks for the component. This one must be added into package as a core component. What about this?

I dont agree, only a very small amount of the users who download joomla will want or be able to translate their site. We dont want to add un-neded bloat to Joomla. A great component, but something which should be made clear its available, maybe from a link in the admin so those who want to translate can download and translate to their hearts content. Maybe also worth adding a link in the joomfish admin panel too.

Also the component should have an export feature, which allows people to export their translation to a central repository so other people can download and use the language file.

Just my 2c though

There's one more thing missing in this great component, and that's a search feature.

This should allow us to search for  text strings, and optionally also definitions. There could be a global search telling us in witch files the string is located, and a search inside files taking us to the right location to edit it.

Since I'm not a coder I don't know how much work this would require to make, but as a translator I know it's needed. Especially for those who just want to edit a front-end string to fit their site better.

I don't agree with Hotnuts. First of all component can be used to customize original translation. You'd be surprised how many English strings can be put in different wording, more suitable for particular website.
Other thing is that English is not the most spoken first language despite of what many people tend to think, and Joomla! has a growing non-English user base. In my opinion it is one of the most important reasons for Joomla!'s success.
Polish version of Joomla! 1.0.13 (full package) was downloaded almost 300k times. Downloads from joomlacode (full package) are blow 600k. Polish native speakers are 43-52M community.

There is an export facility and Translation WorkingGroup uses it constantly. Though it's not so direct as you suggested (generates language sets but has to be uploaded manually). There's no much need for automating it and security reasons are involved.

Roman, thanks for your explanation. I agree with you. Can somebody contact devs about this issue?

As far as I know, this component —as well as Joomfish for example— will not be included in trunk.
Even if the component had been written originally by a core dev, the policy was to not include these in trunk.
Same reason to not include all pdf fonts. A matter of weight of the official package.
I doubt this policy has changed.

pls c the PP

en-GB.xml  CODE

####################################



  English(United Kingdom)
en-GB
1.5.0
Date>2005-10-30Date>
Joomla! Project
Email>admin@joomla.orgEmail>
Url>http://www.joomla.orgUrl>
.....

en-GB.xml  CODE

####################################


English(United Kingdom)
zh-CN
        简体中文(Simplified_Chinese)
1.5.0RC3.1
date>2007-12-12date>
Genous
email>admin@joomla.orgemail>
url>http://www.joomla.orgurl>
.....