Development :  K-Meleon Forum
K-Meleon development related discussions. 
K-Meleon 1.6 translation thread
Posted by: Matt
Date: September 01, 2010 02:12AM

Quick guide for translators

Strings to translate/add:

- hard: to translate embed.jar download localised SeaMonkey build (zip file] and copy the content from chrome > xx.jar > locale > xx (xx = language you translate to i.e. de, fr) to K-M chrome > embed.jar > locale - here create locale folder; do NOT copy all folders from SeaMonkey, only these which are in K-M en-US; now you have to chceck every folder to make sure to copy only the needed files; in some cases you have to translate some strings like branding folder > brand.dtd

- easy: copy kmprefs.jar from K-M 1.5.x to 1.6 preBeta chrome folder; now add new strings to locale XX-yy (translate the text in quotes only):
pref-display.dtd <!ENTITY zoom.label, <!ENTITY zoom.description, <!ENTITY zoom.normal,
pref-filters-dtd <!ENTITY silverblock.enable <!ENTITY flashblock.whitelist, <!ENTITY cssAdblock.edit

- easy: chrome > flashblock.jar > flashblock.dtd > <!ENTITY kmeleon.version

- easy: copy locales folder > XX-yy i.e. Fr-fr, De-de etc. from K-M 1.5.x to 1.6 preBeta root folder > kmeleon.kml > add the english string Toggle Site in Whitelist=your translated text, I added it to # --- docinfo.kmm section and it works.

Remember: add strings with language you want translate to to embed.manifest and kmprefs.manifest. Flashblock.manifest & newsfox.manifest have the strings already.

In order to edit *.jar files change extension to *.zip and "get inside".

I recommend Notepad++ for editing *.dtd, choose Encode in UTF-8 without BOM from Notepad++ menu.

I hope this helps. Feel free to ask.


PS Does anybody know, where to put new strings Dorian mentioned here?



Edited 1 time(s). Last edit at 09/01/2010 02:14AM by Matt.

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: JujuLand
Date: September 01, 2010 02:35PM

The strings mentionned by Dorian must be added in kmeleon.dll

It can be made with ResHacker, but it's not very easy for new translators ...

You can find an explanation on kko's page. There is two manual, one by kko, one by me.

A+


Mozilla/5.0 (x11; U; Linux x86_64; fr-FR; rv:31.0) Gecko/20100101 Ubuntu/12.04 K-Meleon/75.0

Web: http://jujuland.pagesperso-orange.fr/
Mail : alain [dot] aupeix [at] wanadoo [dot] fr




Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: Matt
Date: September 02, 2010 02:06AM

Thanks, JujuLand. I wasn't sure. I made 1.5.x translation 2 years ago smiling smiley

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: desga2
Date: September 02, 2010 02:08AM

k-meleon.dll can be downloaded here: http://kmeleon.sourceforge.net/wiki/kmeleon16
Quote
1.6 Dev wiki page:
kmeleonloc Download (Right click, save link as ... )

K-Meleon in Spanish



Edited 1 time(s). Last edit at 09/02/2010 02:09AM by desga2.

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: guenter
Date: September 05, 2010 06:02PM

Question:
locale/en-US/wallet
locale/en-US/communicator/wallet

folder and files exist twice and are not part of current SeaMonkey 2.x chrome.
Why are they twice - what is using them?
It does not seem to cause problems when they do not exist because You delete them.

Info: The embed/locale/... is part IMHO part of all Firefox 3.x, SeaMonkey 2.x language jars. You can use any except but You need the mentioned wallet files. Do a file compare with a suitable two pane file manager and delete folders and files that do not exist in the K-Meleon chrome. That is IMHO the easiest method.

The subfolder ./branding contains brand.dtd that is unique to K-Meleon! Copy it over unchanged.

The subfolder ./global-region contains region.properties that are unique for/to K-Meleon.

In the following content the red text must be translated!
The (blue) URL leads currently to a post with links in the Extensions forum.
The original URL led to the Firefox extension page which K-Meleon cannot use!
We may want to change this K-Meleon Forum URL to a translated page that explains the topic/extension page a bit?

You may want to localize the location (green) of plugindoc.mozdev.org.
AFAIK versions exist in cz | de | en | es | fr | ja | nl | pl | zh.
E.g. German: http://plugindoc.mozdev.org/de-DE/ is an entry to localized versions. Click the link and then change language to get Your local version's URL.



region.properties:

#
# Localizable URLs
#
pluginStartupMessage=Starting Plugin for type

# plug-ins URLs
more_plugins_label=K-Meleon Extensions
more_plugins_url=http://kmeleon.sourceforge.net/forum/read.php?9,94027
plugindoc_label=plugindoc.mozdev.org
plugindoc_url=http://plugindoc.mozdev.org/



Edited 2 time(s). Last edit at 09/06/2010 03:13AM by guenter.

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: desga2
Date: September 06, 2010 05:14AM

Quote
guenter
Question:
locale/en-US/wallet
locale/en-US/communicator/wallet

folder and files exist twice and are not part of current SeaMonkey 2.x chrome.
Why are they twice - what is using them?
It does not seem to cause problems when they do not exist because You delete them.

Info: The embed/locale/... is part IMHO part of all Firefox 3.x, SeaMonkey 2.x language jars. You can use any except but You need the mentioned wallet files. Do a file compare with a suitable two pane file manager and delete folders and files that do not exist in the K-Meleon chrome. That is IMHO the easiest method.

Files in \wallet subfolder on embed file are identical, but you must use \wallet and delete \comunicator\wallet, because it is the used by the embed.manifest file:
locale	wallet	en-US	jar:embed.jar!/locale/en-US/wallet/
I think remember wallet is "Remember Password" feature, not more included like "wallet" in Mozilla products with Gecko 1.9.x.

Really you can use locale files from Firefox 3.5.x or Seamonkey 2.0.x.
The files be should similars, but we usually (at least in before versions) use Seamonkey files for chrome and locales. (I don't know if we should change it now for Gecko 1.9.x, I don't know if Firefox files are better than Seamonkey)

When K-Meleon 1.6 beta will be released I'll builded a localization package for translations.

K-Meleon in Spanish

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: guenter
Date: September 08, 2010 12:26AM

Quote
desga2
Quote
guenter
Question:
locale/en-US/wallet
locale/en-US/communicator/wallet

folder and files exist twice and are not part of current SeaMonkey 2.x chrome.
Why are they twice - what is using them?
It does not seem to cause problems when they do not exist because You delete them.

Info: The embed/locale/... is part IMHO part of all Firefox 3.x, SeaMonkey 2.x language jars. You can use any except but You need the mentioned wallet files. Do a file compare with a suitable two pane file manager and delete folders and files that do not exist in the K-Meleon chrome. That is IMHO the easiest method.

Files in \wallet subfolder on embed file are identical, but you must use \wallet and delete \comunicator\wallet, because it is the used by the embed.manifest file:
locale	wallet	en-US	jar:embed.jar!/locale/en-US/wallet/
I think remember wallet is "Remember Password" feature, not more included like "wallet" in Mozilla products with Gecko 1.9.x.

Really you can use locale files from Firefox 3.5.x or Seamonkey 2.0.x.
The files be should similar, but we usually (at least in before versions) use SeaMonkey files for chrome and locales. (I don't know if we should change it now for Gecko 1.9.x, I don't know if Firefox files are better than SeaMonkey)

When K-Meleon 1.6 beta will be released I'll builded a localization package for translations.

Ok, I'll delete that ./communicator/wallet.
And take the translated wallet files from K-Meleon 1.5.4. ;)

Using SeaMonkey files is easy for ES, PL, DE ... where the SeaMonkey translation exist smiling smiley

I was thinking about the other languages where the SeaMonkey translations do not exist.
Kairo.at mentioned AFAIRemember that he used toolkit translation strings from Firefox.

I will dig into it & try with German.
Firefox files are not better - in theory they should be identical.(1)
At least those for/in toolkit.jar.
Pippki files may have translation problems/different strings?

We will see when You have build the translation package for the beta.

(1) Now! For GRE 1.9 and later!
It was different until GRE 1.8.



Edited 1 time(s). Last edit at 09/08/2010 02:42AM by guenter.

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: Matt
Date: September 18, 2010 04:17PM

Quote
guenter
You may want to localize the location (green) of plugindoc.mozdev.org.
AFAIK versions exist in cz | de | en | es | fr | ja | nl | pl | zh.
E.g. German: http://plugindoc.mozdev.org/de-DE/ is an entry to localized versions. Click the link and then change language to get Your local version's URL.



region.properties:

#
# Localizable URLs
#
pluginStartupMessage=Starting Plugin for type

# plug-ins URLs
more_plugins_label=K-Meleon Extensions
more_plugins_url=http://kmeleon.sourceforge.net/forum/read.php?9,94027
plugindoc_label=plugindoc.mozdev.org
plugindoc_url=http://plugindoc.mozdev.org/

The whole site http://plugindoc.mozdev.org/ hasn't been updated since march 2009; nl, pl, zh don't even exist (page not found).
The worst thing about the site: it links to horribly outdated plugins versions like Flash Player 10.0.12.36 or JRE 6.0 Update 14.
My humble suggestion: replace plugindoc.mozdev.org with corresponding URL

https://addons.mozilla.org/de/seamonkey/browse/type:7 de
https://addons.mozilla.org/en-US/seamonkey/browse/type:7 en-US
https://addons.mozilla.org/es-ES/seamonkey/browse/type:7 es-ES
https://addons.mozilla.org/fr/seamonkey/browse/type:7 fr
https://addons.mozilla.org/pl/seamonkey/browse/type:7 pl
https://addons.mozilla.org/ru/seamonkey/browse/type:7 ru


Quote
guenter
In the following content the red text must be translated!
The (blue) URL leads currently to a post with links in the Extensions forum.
The original URL led to the Firefox extension page which K-Meleon cannot use!
We may want to change this K-Meleon Forum URL to a translated page that explains the topic/extension page a bit?

Mayby we couldn't have to change this URL http://kmeleon.sourceforge.net/forum/read.php?9,94027. Mayby we could simply translate the content to de, es, pl etc. and You, guenter, could then edit Your post.


Localisators & everyone, what do you think about it?

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: guenter
Date: September 18, 2010 05:40PM

Quote
Matt


The whole site http://plugindoc.mozdev.org/ hasn't been updated since march 2009; nl, pl, zh don't even exist (page not found).
The worst thing about the site: it links to horribly outdated plugins versions like Flash Player 10.0.12.36 or JRE 6.0 Update 14.
My humble suggestion: replace plugindoc.mozdev.org with corresponding URL

https://addons.mozilla.org/de/seamonkey/browse/type:7 de



Quote
guenter
In the following content the red text must be translated!
The (blue) URL leads currently to a post with links in the Extensions forum.
The original URL led to the Firefox extension page which K-Meleon cannot use!
We may want to change this K-Meleon Forum URL to a translated page that explains the topic/extension page a bit?

Mayby we couldn't have to change this URL http://kmeleon.sourceforge.net/forum/read.php?9,94027. Mayby we could simply translate the content to de, es, pl etc. and You, guenter, could then edit Your post.


Localisators & everyone, what do you think about it?

The German URL's https://addons.mozilla.org/de/seamonkey/browse/type:7 de text is mostly English sad smiley So I'd prefer plugins.doc with 2009's links.

"Extension" is not a German word - I'd change it to "Erweiterungen"

IMHO it is ok t open the sticky extension thread for translations?



Edited 1 time(s). Last edit at 09/18/2010 05:58PM by guenter.

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: desga2
Date: September 18, 2010 07:44PM

I think the same solution is possible for both problems:

1) Plugins website link can be changed to an updated version of this wiki page: ThirdPartyPlugins
This can be localized and could have links to both:
http://plugindoc.mozdev.org/
https://addons.mozilla.org/en-US/seamonkey/browse/type:7

Also this wiki page is referenced by Resources wiki page.

2) For Extensions, we can create a new wiki page with similar text to Extensions Sticky in Extensions forum.

Also this wiki page must be referenced by Resources wiki page.


The way more easy for localizations of websites is the wiki method, this already implemented in K-Meleon site, why not use it?

K-Meleon in Spanish



Edited 1 time(s). Last edit at 09/18/2010 07:45PM by desga2.

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: guenter
Date: September 18, 2010 09:31PM

Quote
desga2
I think the same solution is possible for both problems:

1) Plugins website link can be changed to an updated version of this wiki page: ThirdPartyPlugins
This can be localized and could have links to both:
http://plugindoc.mozdev.org/
https://addons.mozilla.org/en-US/seamonkey/browse/type:7

Also this wiki page is referenced by Resources wiki page.

2) For Extensions, we can create a new wiki page with similar text to Extensions Sticky in Extensions forum.

Also this wiki page must be referenced by Resources wiki page.


The way more easy for localizations of websites is the wiki method, this already implemented in K-Meleon site, why not use it?

Was just my suggestion, desga2 You are the dev that is finally deciding it all.

Ok, that sounds to me like the better idea anyway.

Change the URLs in region.properties similar to below then?


For 2. Just place a copy of the post
http://kmeleon.sourceforge.net/forum/read.php?9,94027
to the wiki and reference that instead.

That text in the post exists already.
(Maybe ndbord or another en speaker can check the wording else we leave it?)


pluginStartupMessage=Starting Plugin for type

# plug-ins URLs
more_plugins_label=K-Meleon Extensions
# place acopy somewhere in wiki?
more_plugins_url=http://kmeleon.sourceforge.net/forum/read.php?9,94027
# just use our name and place?
plugindoc_label=ThirdPartyPlugins
plugindoc_url=http://kmeleon.sourceforge.net/wiki/ThirdPartyPlugins


Is that what You have in mind?



Edited 1 time(s). Last edit at 09/18/2010 09:46PM by guenter.

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: Matt
Date: September 19, 2010 12:16AM

Quote
desga2
1) Plugins website link can be changed to an updated version of this wiki page: ThirdPartyPlugins
This can be localized and could have links to both:
http://plugindoc.mozdev.org/
https://addons.mozilla.org/en-US/seamonkey/browse/type:7

How about Browser Plugins? Perhaps we could link to this section, too.

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: desga2
Date: September 19, 2010 08:27AM

@ guenter:
Yes it's the idea.

@ Matt:
Yes can be added too.

This is the wiki page for Extensions: (Under construction)
http://kmeleon.sourceforge.net/wiki/Extensions

K-Meleon in Spanish

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: Alex.Tarantul
Date: November 25, 2010 12:44AM

Now 1.6beta translated on russian (chrome and locales).grinning smiley
It is ready for use.

My blog about K-Meleon
http://kmeleon-ru.blogspot.com/

Options: ReplyQuote
Re: K-Meleon 1.6 translation thread
Posted by: desga2
Date: November 25, 2010 03:42AM

Thanks Alex, but I didn't release a translation package yet because I'm working in Beta 2 and some strings changed.
I'm sorry sad smiley

K-Meleon in Spanish



Edited 1 time(s). Last edit at 11/25/2010 03:42AM by desga2.

Options: ReplyQuote


K-Meleon forum is powered by Phorum.