I'm translating K-Meleon in italian, I've already completed all submenus and tollbar hints but I'd like to translate every menu and configuration window. Which files am I supposed to manipulate in order to completly translate K-Meleon?
Kind regards,
-Zaltar

Oh, it's K-Meleon 0.9.12 of course.

Uhm... I found out that some english us *.jar files got the XML codes which draw many messages of K-Meleon, maybe all the untranslated words I was looking for.
We'll see...

Ok, pretty good results till now.
That jar files weren't related to any menu, the answer was in the function callings: so I actually translated ALL menu and ALL submenu in ITALIAN.

To translate:
1) View => Toolbars => Bookmarks and so on, those check buttons, I don't know where they are hidden XD
2) Every configuration window, again I don't have a clue what I gotta do.

Well, uff, maybe I should seek some answers in the Development Forum, 'cause here I'm getting just no help from anybody... I guess I should move there...

@Zaltar,

look at my post here: http://kmeleonbrowser.org/forum/read.php?f=2&i=5031&t=5031

You have the way for chrome (except extensions on which I'm working)

1) For the toolbars name, you have a part in toolbars.cfg, and another part in kplugins, and the translation is not too much easy, because you must go in with an hex editor.

2) don't understand... perhaps kplugins ??

A+

The toolbars are hidden in skin/ (folder) toolbars.cfg.

The jar files that You found. are for some not so often used things.
You can use the chrome jar files from any 1.7.x Italian Mozilla.

You can reduce them (select the file that is in corresponding english) jar so they have only the files that are in en-us.jar en-win.jar and Us.jar.
the files corespond with:it-IT.jar, it-win.jar and IT.jar.
if You do it like that also replace in installed-chrome.txt
the mentioned en with it and every US with IT.

else You translate the English inside the jars and keep the names.

there might be also it versions of aggreg8.jar ... and other jars (which has many translations inside have a look a ff extensions page perhaps - You will find them inside the jar / jar is just another name for zip). The italian of mtypes editor comes from Pref panel (in case You want to use that I can look up exact location - just tell me).

If You translate chrome Yourself make sure to save as encoding="UTF-8"
(some laguages like German, French or Spanish typical letters and need it maybe italian too)

Maybe do macros, menus and accel.cfg not from English version but from Spanish or French or one of the other translations (that is easier if You speak the language). But I gather You have translated that already - but if any remains ...

The English inside some dll and the exe can be done with a resource hacker.

Future:
The translated menus and macros.cfg of 0.9 can be used with little alteration for k-m 1.0 also. dll and exe will be easier to translate with 1.0 since Dorian made a file that contains the strings (but the 1.0 is not officially issed yet - Mozilla chrome for the 1.8.x SeaMonkeys does not exist in Italian yet - but will exist later?).

greetings to IT from DE and wellcome here

also this was posted when Spanish was translated.
http://kmeleonbrowser.org/forum/read.php?f=4&i=6011&t=6011
maybe it is helpfull for You.
Sorry that i did not think of it imidiately.

@guenter,

Things are simplest now than with the first translation I realize, due to the fact that locale chrome are now avalaible with a minimum of needed modifications (I think I''ve already gave it, but if not, I'll try to keep my notes and send it again).

I've found the folder where to keep locale for K-Meleon 1.0 (I think it's the same gecko version):

http://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/1.0/contrib-localized/

Take the xpi file and extract your locale file (for example: AT.jar, de-AT.jar and de-win.jar)

We can apply the same process to translate chrome from K-Meleon 1.0 as we do with 1.7.12 (I haven't found the same for 1.7.13, that's why I keep 1.7.12)

A+

Hi alain,
At the moment i write internet pages - so i have littel time for k-m.
But I have a complete de-AT SeaMonkey 1.8. to use the composer ; ).

Zaltar (---.41-151.net24.it) is doing 0.9.12. AFAIK all 1.7.x translations work with 1.7.13 or 1.7.12 chrome - there seems to be no changes in the chrome language files between the 1.7.x versions.

The SM 1.8 x chrome language files will probably also work with all 1.8 versions.

de-At was the first translation available for SM 1.8 (one of the leading translators is Austrian - i never have to worry about chrome translations because the menus are identical in de-DE). fr-FR, es-ES, pl-PL were also available for SM 1.8 very early.
greetings to FR - from DE



p. s. i hope to go to Southern France or Normandy for vacation this summer : )

Mumble mumble, the infos you provided are being processed hoping my brain can compute them.

But I have a complete de-AT SeaMonkey 1.8. to use the composer ; ).

Isn't Nvu better to compose page ??

A+

@Zaltar - sorry. if You want i can download a it-IT Mozilla 1.7.x if available
and try to do the "it" chrome as far as it is available.

I can not speak much foreign languages but i can try to help with "it" chrome
->You have to check later. big grin.

I am very impressed that You are so far with Your translation so soon!

I assume You have the same problem as we all have. Lack of time.
If You have questions - we will try to answer all - if we know the answer.
This is a small community - i will try to do my best. and so do all here.

btw. alain is the most expert translator. he is doing the French version.
That why he knows all the places - where translation work is needed.

i am not a good translator but know some html and some little things about chrome.

@alain: You are right as always. Nvu is better !
but i downloaded SM to have the chrome for k-m.
i do most html coding with the editor that is inside my file manager (eXec);
but some times I need a source code view and real view and the Mozilla that
has the chrome that belongs to the k-m i am using is always downloaded : )

greetings You two

I have lack of time, I'll handle this project as soon as I can I guess.

I was initially positivly sorprise about the simple access to the code, but now I realize that a lot is hard to work with: changing every message and so on isn't an easy task.

Plus I found out that find a text directly typing it isn't working and there's no feature to open a background tab using the middle mouse button.

K-meleon is pretty quick as parser but still lack some feature of Firefox, actually my favourite browser.
I hope what I said will be considered as an opportunity of improvement and not just like a futile criticism.
Kind regards.

> Plus I found out that find a text directly typing it isn't working and there's no feature to open a background tab using the middle mouse button.

Oh, both can be done in K-Meleon.

1) Change accessibility.typeaheadfind.linksonly to false.

2) In accel.cfg change
MButton = layers(OpenLink)
to
MButton = layers(OpenLinkBg)

Damn, these need to be documented in the site.

> Oh, both can be done in K-Meleon.
Oh, my gosh, so easy!
Just a little question: how am I suppose to perform a "next result" in direct typing text search?

Nice, "next result" is F3 just like in the common text search.