localised alphabet drop-down list

[lordy]

@akaman - full i18n/localisation is coming soon. Not this main release - possibly the one after along with subtitle downloading.

[akaman]

(01-13-2011 10:23 PM)lordy Wrote:  @akaman - full i18n/localisation is coming soon. Not this main release - possibly the one after along with subtitle downloading.

wow it is perfect.so thanks lordy.

p.si.:i hope you dont forget new realese for dark over.config pages problem..we would like to test it.before csi update.

[Roman_V_M]

(01-13-2011 10:23 PM)lordy Wrote:  @akaman - full i18n/localisation is coming soon. Not this main release - possibly the one after along with subtitle downloading.

For that it would be better if you consolidate meaningful text into as few files as possible, preferably in XML format like this:
en_US.xml

Code:

<strings>
<string="1">Director:</string>
<string="2">Writer:</string>
<string="3">Cast:</string>
...
</strings>

It would simplify GUI translation process - you won't need to sift through a lot of files scattered among different folders to find the strings to translate , and localization professionals like me will be able to use proper CAT tools.

[lordy]

IMO XML is for machine to machine - not for human editable files

I'll probably use GNU gettext ( http://en.wikipedia.org/wiki/GNU_gettext )

If not I'll just use something similar to the java properties/resource files:

keyword=text ...

eg.

Code:

rescan=....
misscellaneous=
scan_message=This will return immediately and start a background scan of the listed paths. Scan speed is approx 300 new files per hour (x2 if getting fanart). Other applications may also affect overall scan speed. Covers and fanart are downloaded independently so may appear later.

With one resource file per language/locale

[Roman_V_M]

2lordy

Code:

IMO XML is for machine to machine - not for human editable files

A NMT player IS a machine.
For amateur translators there's no difference - they will need to use some text editor like notepad2 or notepad++ to insert their translations in any case, but as a professional I'd like to be able to use CAT tools like Trados to streamline the process and re-use translations for different components and versions. As far as I can tell, GNU gettext format is not very good for translating with CAT and also is not very good at all if the number of strings exceeds 20-30 - managing such translation is hell, believe me.

[lordy]

> and also is not very good at all if the number of strings exceeds 20-30

Could you elaborate on that?

Code:

<string="1">Director:</string>

Presumable the labels '1' etc dont have to be numbers. I dont want to write code with cryptic numbers all over the place instead of keywords. It's cryptic enough as it is

Will the following be OK?

Code:

<string="director">Director:</string>

But I'll probably still have:
director:Director

Because, XML is useful for tool-to-tool integration but not parsing efficiency. I'll be reading the resource file at every page load.
It shouldn't be too hard to knock up a script to convert the flat files to XML for your needs

That's one reason I feel the pain for YAMJ skinners, XSLT is truly yucky to write without any tools

[Roman_V_M]

(01-14-2011 02:14 PM)lordy Wrote:  > and also is not very good at all if the number of strings exceeds 20-30

Could you elaborate on that?

OK, maybe I overcomplicate things. What I trying to say that a format used for storing GUI strings should allow to strip meaningful text from service strings, variables and tags. I mentioned XML only because it's used in large software to store GUI strings and there are some tools to process this format.

Quote:Will the following be OK?

Code:

<string="director">Director:</string>

Yes, it will work, but I think what you suggest below is much better:

Quote:But I'll probably still have:
director:Director

Such strings can be easily processed even in MS Excel or imported in CAT (Computer Assisted Translation) tools of necessary.