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.
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.
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.
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://kmeleonbrowser.org/forum/read.php?9,94027
plugindoc_label=plugindoc.mozdev.org
plugindoc_url=http://plugindoc.mozdev.org/
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?
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://kmeleonbrowser.org/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?
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?
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