I have quickly finished the french translation of kml and dll, as it's very near from, or exactly the same translation as I did for 1.6.0b.

But I have a problem to translate the jar file.
I know how it works, it's not the problem, but loading the french Firefox version, doesn't give some jar file, and I don't know how and where to keep strings.

Do I must install, and keep string for Firefox execution, or do setup will create such jarfiles ?

Concerning the setup, do we use the previous one which works except for setting default brother ?
Naruman seems to have a solution, but I don't like using msi (it doesn't work under Linux)
I we take the one I know, I'm ready to update it. I just before see if my packager is always working, what I think.
It will be able to create en and other language packages.

The jar file is a mix between:
- firefox /omni.ja!/chrome/XX/locale/XX (so you must unzip omni.ja to get the localized files)
- and kmeleon /browser/omni.ja!/chrome/XX/locale

I'm still unsure on how I'll handle it for the localized installer.
But you can already test your translation. You just need to add in chrome.manifest:

manifest locales/xx/xx.manifest

Both omni.ja should be repacked with the translations for the localized installer, and I may script the repackaging ( depends if I'm lazy or not :\ )

If I'm not clear, you can email me

Now for the installer, I like how the firefox installer do a proper job, like creating an uninstall log file [rant] something that NSIS would do if it was a real installer maker [/rant]. And like I said, helper.exe can replace setdefault for file association [rant] something that could be done easily if NSIS was a real installer maker [/rant].

But If you're up to update the previous installer, this could be easier to use.
Firefox installer is already translated but in the properties format (see french version). So they need to be converted to .nsh

QuoteJujuLand
I have just for now a request about skins.
Except with classic, the privacy bar doesn't have text.
I have this problem since 1.60b

Privacy toolbar use images because toolbars.cfg doesn't support image and text at the same time. It was different in 1.5? I don't remember.

No, that's not it, privacy button texts have always been "painted text" as long as I can remember.
Not sure about Linux, but on my Win98 it depends only on the bitmap type, not the used KM version. Most skins work, like Phoenity, in all KM versions, just not a few skins, like AuraAlpha, which don't work in any KM version on my machine.

When I open the problematic bitmaps in IrfanView, that can't show the text either - it's like black text on black background.
If I recall correctly from years ago, some of the toolbars and buttons from AuraAlpha did show up fine, although the working ones had slightly rough borders around the symbols. So my guess was those probably use "full" transparency only, while the privacy bitmaps who show up black in black are using various "shades" of transparency? Could be for better antialiasing of the text or such. And gradual transparency my system just can't seem to display. Perhaps Jujus Linux version neither, but don't know.

For affected users it would be possible to work around by modifying the transparency type with irfanview, if only they didn't happen to be painted black-on-black. Instead, black on dark-dark-dark gray should be possible to modify for users, in theory.

PS: The privbar in the 1.5 default skin Phoenity works fine too, not just Klassic (which has way too tiny text).
And if anyone needs more or smaller buttons, my classiria skin contains a slightly modified and extended version of the Phoenity privbar. Numbers and names all the same, only the button width needs to be adjusted in toolbars.cfg

PS2:
DORIAN - please consider switching on the privbar out-of-the-box! It's the only one toolbar that is hidden by default, although it's one of the unique great features of KM. For me THE killer feature, along with macrolanguage, why I absolutely refuse to use another browser at all.
Hiding something later is always easy, if someone doesn't like it, but getting newbie users to even switch it ON and have a look is often kinda hard. They just don't seem to get it what we're talking about, because they don't know it from other browsers, and "privacy" doesn't really give any idea what it's about.

I 'm a little behind on the current status for the localization effort. I remember I did an un-finished Simplified Chinese local a while ago (maybe around 1.0 time). How hard it is to convert it into the format for 74?

I have a suggestion to fix peoblesm with skin toolbar configuration in K-Meleon 74Beta2.

1. Favorites and Hotlist should be enabled by default in kmeleon.js to fix configuraion problems.
2. Every toolbar visible in prefskins.js and skins.js under defaults to placement amd size of teh toolbars
3. Every toolbar should be visible in each skins,js under skins folder for each to fix problems with toolbar placement in each skins.
4. Change the default skin the kmeleon.js to fix each skin and delete the profile after you fix a skin.
5. Repeat Step 4 until you fix each skin.
5. You change the default skins back to orginal skin in kmeleon.js after all the fixes.
6. You change visibility back to nortmal values in prefskins, and each skin.js after all the fixes with the skins are done.

The values to that need to be are are the ones related to size and placement of toolbars in prefskin.js and each skins.js

With this method you should be able to fix problems with default skin.js, prefskins.js, and skins.js in each skin folder in K-Meleon 74 Beta2

QuoteHao Jiang
I 'm a little behind on the current status for the localization effort. I remember I did an un-finished Simplified Chinese local a while ago (maybe around 1.0 time). How hard it is to convert it into the format for 74?

A K-Meleon 1.6.0 zh-CN locale translation was posted in the Forums November 16, 2011 by Chanson Yu:

QuoteJujuLand
I have just for now a request about skins.
Except with classic, the privacy bar doesn't have text.
I have this problem since 1.60b

Privacy toolbar use images because toolbars.cfg doesn't support image and text at the same time. It was different in 1.5? I don't remember.

No, that's not it, privacy button texts have always been "painted text" as long as I can remember.
Not sure about Linux, but on my Win98 it depends only on the bitmap type, not the used KM version. Most skins work, like Phoenity, in all KM versions, just not a few skins, like AuraAlpha, which don't work in any KM version on my machine.

AFAIK It is not a fault of the skin bitmap but true transparency is realized/made with a Windows function that is not present in Win98 and some Wine versions.
If really a Win98 version is done a skin with magic pink must be created. Actually the magic pink version used to exist but its hot bmps were done 1 pixel down instead of lighter colors. I think I could send You the half finished work.
I probably still have some of the prototypes.

It cannot IMHO not be done with Irfan View.

You have to repaint the transparent pixels with magic pink with a picture editor.

QuoteJujuLand
Hi Dorian,

I have quickly finished the french translation of kml and dll, as it's very near from, or exactly the same translation as I did for 1.6.0b.

But I have a problem to translate the jar file.
I know how it works, it's not the problem, but loading the french Firefox version, doesn't give some jar file, and I don't know how and where to keep strings.

Do I must install, and keep string for Firefox execution, or do setup will create such jarfiles ?

Concerning the setup, do we use the previous one which works except for setting default brother ?
Naruman seems to have a solution, but I don't like using msi (it doesn't work under Linux)
I we take the one I know, I'm ready to update it. I just before see if my packager is always working, what I think.
It will be able to create en and other language packages.

Thanks
A+

I do not have a 1.6 de-DE translation to start and have some questions.

Are the strings in the K-Meleon native chrome the same as in 1.5.4?

The kml seems exactly the same. It repopulated completely from 1.5.4 kml using kko's script. Is this correct?. Or did I overlook something?

I did kmeleon.dll. Not many differences. 3 or so so different strings some not existing any more. Or did I overlook something?

I understand that I can use the kplugin dll from 1.5.4 de-DE.
Or did I overlook something?

omni.ja The same problem here. What tools and commands unpack/pack it?

QuoteguenterAFAIK It is not a fault of the skin bitmap but true transparency is realized/made with a Windows function that is not present in Win98 and some Wine versions.

If you call it "true" transparency then this works fine on all systems. No prob! We do NOT need magic pink, every other color works just as well. What I've been trying to tell since years, but old legends are hard to get rid off.
The prob is only "gradual" transparency in % degrees other than zero or 100%. In old threads I had screenshots of AuraAlpha where it clearly showed that many buttons *are* shown transparent, allthough ALL buttons have a black background set to transparent. The transparent black only doesn't work in bitmaps defined with gradual transparency for (I suppose) better antialising of the text in them.

When opening privhot and privcold with Gimp, I see text.
I have edited it:
removed color to Transparency,
paste a color other than white (in fact the grey of the toolbars)
set again color to transparency
and saved

Now it's ok.
Can you test it with your own versions of windows ?
This modifications are ok for all Alpha skins (they use the same files)

I noticed also that a few icons had bad transparency too, I think it's due to the same reason.
I think that the program which generated these pictures was a little buggy.
I'll try to apply the same treatment, and I'll test it.
If ok, I will have send it modified.

When opening privhot and privcold with Gimp, I see text.
I have edited it:
removed color to Transparency,
paste a color other than white (in fact the grey of the toolbars)
set again color to transparency
and saved

Now it's ok.
Can you test it with your own versions of windows ?
This modifications are ok for all Alpha skins (they use the same files)

I noticed also that a few icons had bad transparency too, I think it's due to the same reason.
I think that the program which generated these pictures was a little buggy.
I'll try to apply the same treatment, and I'll test it.
If ok, I will have send it modified.

A+

alain & siria. I know that a Windows NT function was used for transparency from the time I tried to compile K-Meleon.exe and kplugins. It supports AFIK partial transparency. Dorian wanted to achieve that we can use Firefox skin bitmaps almost out of the box.

I cannot test with Windows 98 or Wine.

alain's 2 test files give me no trouble under XP SP3.

privcold and privhot were done by disrupted with Gimp.
It is a buggy program - if You say so.

The pics do not have bad transparency - Your systems just do not support transparency the way NT systems do.

Most pics were ported from png to bmp by me. I used magic pink originally and they do not need transparency really. Only the reload button in the 16 pic/small skin can not be done like this in a really satisfactory way and the same is true for the same icon in Large. That is why disrupted created another simpler icon. But Dorian wanted the original.

It was expected that Win98 support would be dropped when K-Meleon moved to 1.6 because the Mozilla GRE did not support it. Then the Kernel-Ex project stepped in.

This Phorum is a pain in the... For the last 15 minutes I tried to upload a sample pic to the graphics section and post. All I get. And I also have this trouble with normal posts.

QuoteLeah
The disappearance of the end line of toolbars that creates a distinctive line between the page content and interface is it like a bug or intended? if it's intended, I don't think it's visually appealing at all(at least to me). It looks as if the toolbars are cut out at the ends. Hope if it is a feature there will be a setting to restore the old toolbars.

What OS ? There was two lines before, but I had to remove one for fullscreen. It's fine for me with W7.

The structure isn't surprising.
I suppose that the translation must be located in chrome.
We must probably copy the folder en-US to fr-FR (for me), and en-US.manifest to fr-FR.manifest
And then modify fr-FR.manifest and translate fr-FR/locale/*.dtd and properties
In chrome/kmeleon/content/console2 and flashblock, I found dtd files.
Are they to translate too?

What is the folder _console2 ? an old version to remove ?

After, we have then just to pack in zip format without compress, and rename it omni.ja

@George Hall please note that using a bit map twice (as both cold-image and dead-image) is sometimes better, because it allows the images to remain stable when you move them. My skins\AuraAlpha(Compact) &Main Bar begins:

So Linux works better, but win98se still shows only black with Gimp22.

QuoteJujuLandI have edited it: removed color to Transparency, paste a color other than white (in fact the grey of the toolbars), set again color to transparency and saved. Now it's ok. Can you test it with your own versions of windows?

Thanks for trying, the text is readable, but now there is no transparency any more. The gray background is opac.

Sorry, you said "hang", I misunderstood.
About your question why I'm using gecko 24, that's because this version will be updated with all the security fixes for a while.

@jujuland
Yeah I forgot to remove _console2, the dtd outside locale don't have to be translated. You're right about omni.ja, except you have to do both. But for now I would like you to just make the jar file, like the one in the locale package, so I can make some tests and finalize the translation process.

QuoteJujuLand
Choosing fr-FR, does the trick, and K-Meleon nativ boxes are translated.
But kml is not used.

Is-it due to the fact that I haven't yet translated chromes ?

There is too much off topic gibberish in this thread. You overlooked that I already posted that if You use the main.kmm from 1.6 beta it toogles to menues to German and other languages kml in their locales ok.

QuoteguenterI found that using the main.kmm updated by desga2 on the 28.11.2010 will allow me to switch the language to German permanently. I did not find out why.

But I suggest we use all his 1.6 kmm and menus as basis for the current work. There is no reason to reinvent the wheel.

Before that I had complained in another thread that it does not find kmeleon.kml.

BTW desga2 menues.cfg fixes that right click does not work on some skins and situations.

Each new vesions of K-Meleon that uses the line
<script type="application/x-javascript" src="chrome://kmprefs/content/kmprefs/DefaultBrowser.js"/>
to set the default browser in kmrefs in the pref-browsing.xul.

I will delete all the kmprefs files and use the kmprefs from K-Meleon 1.6.0Beta2

and use its method of setting the default browser.

Replacing "CurProcD" with "GreD" in the line
proc.init(getFile(getFolder("CurProcD"),"SetDefault.exe"));

which gives the line
proc.init(getFile(getFolder("GreD"),"SetDefault.exe"));
in pref-browsing.xul.