Open Oceanwatcher opened 13 years ago
Oceanwatcher
commented
13 years ago Created attachment 688
Example of .ini language file for a Joomla extension
Notice there is a header and sometimes comments in between the strings.
The header is embedded like this:
/* some text here /
but can also be pre-fixed by # like the comments further down. I know it is obvious to all of you programmers, but too much information never hurts?
dwaynebailey
commented
13 years ago Svein: Would you be able to test Virtaal in trunk? We have added a feature for monolingual formats. At the moment this is only ODT files, but the framework is in place. WOuld you be able to look at this and check if it meets your ini requirements?
dwaynebailey
commented
13 years ago (In reply to BZ-IMPORT::comment #1)
Created an attachment (id=688) [details] Example of .ini language file for a Joomla extension
Unfortunately this look like yet another INI format :(. So we'll need to fix those first before we can get other things working.
There is a cli tool that is part of the translation toolkit for converting to and from .ini files.
It would make this tool a lot more accessible to have it as an import/export option in Virtaal.
A lot of translators are not programmers at all and the main reason for requesting this is that Joomla, an open source CMS, uses .ini files as the format for their language files. It is the biggest cms in the world (as long as you do not count WordPress as a CMS...) with millions of users. In addition to the core files, there are well over 5000 extensions that needs translation and there are frequent updates.
To make the translation workflow easier would definitely help getting good tools for websites out into every corner of the world.
The format of the filenames are:
en-GB_extension-name.ini
Each language has their own folder named according to the language - en-GB, nb-NO etc. There is usually always a file in English that we use as a starting point. I will try to upload an example of such a file.