Language Pack ...

[ioc2e3]

Please provide ...

Used on Basilisk Browser ...

Traditional Chinese Language Pack ...

.

[ioc2e3]

Pale Moon Browser's language packs ...

After installed on Basilisk Browser ...

No work at all ...

.

[Moonchild]

Language packs for one browser don't work on a different browser. Common sense, no?

[ioc2e3]

Ask this because ...

Basilisk is pretty close to Pale Moon ...

.

[Moonchild]

And a poodle is pretty close to a wolf.

[Basilisk-Dev]

Please provide translations ...

Then I will make the language pack ...

I do not speak Chinese ...

[ioc2e3]

Excuse me ...

Basilisk Browser's ( language file ) ...

Where is ( file path ) ?
What is ( file name ) ?
Can it be displayed normally on Notepad++ ?

.

[gabrgv]

As I recall, people have requested language pack for the following languages: chinese, spanish, german and russian; and some have offered help on writing them. But it’s not that easy to download the Iceweasel-UXP langpack, find out the differences between them, etc. I once tried to write a portuguese langpack following the steps mentioned here and there but to no success. It’s hard for a complete lamer like myself to do this kind of thing.

It would be very convenient if you created a reference langpack, as mentioned here:

So maybe should create a repo with a reference language pack for Basilisk as well? In this case, I think there will be a better chance that someone will translate it into other languages.

[_yup_]

So maybe should create a repo with a reference language pack for Basilisk as well?

The "reference" (en-US) language pack can be easily extracted from the Basilisk with any command line ZIP archive decompressor.

This is an example for the Info-ZIP unzip:

Code: Select all

unzip -C -d _LangPack                 omni.ja         chrome/en-US/* chrome/chrome.manifest
unzip -C -d _LangPack/chrome.manifest browser/omni.ja chrome/en-US/* chrome/chrome.manifest

Run it from the Basilisk app directory, and it will create the _LangPack subdirectory with all necessary files.
Then edit extracted chrome.manifest and browser/chrome.manifest files - remove all lines, that do not start with "locale".

The last step is creation of install.rdf file (using any existed language pack as a template) and chrome.manifest with two lines:

Code: Select all

manifest chrome/chrome.manifest
manifest browser/chrome/chrome.manifest

(But it is preferable to rename extracted chrome.manifest's to en-US.manifest.)

But creation of a language pack for one browser using a language pack for some other browser is not so straightforward as one might think.
(I am the creator and maintainer of language packs for Mypal and Iceape-UXP, so I know how much efforts takes creation of initial translation. Updating of an already existent one is way easier.)

[ioc2e3]

The "reference" (en-US) language pack can be easily extracted from the Basilisk with any command line ZIP archive decompressor.

That ...

Downloaded from here ( https://sourceforge.net/projects/infozip/ ) ...

.........................

After decompression ...

No .exe file was found on the decompressed folder ...

.

[Bilbo47]

That's a source code project, not a downloadable program. Instead try 7-zip