Franck's Personal Server
|
|
As former IPCop developper and seeing absence of release for IPCop 1.4 since some years, I have decided to put out the 1.4.23 update!
You will find here necessary fixes to build your own 1.4.23 from the cvs. You will also found the complete patches to upgrade your IPCop.
Installation is easy
DO NOT USE WITH SCSI ! DUPLICATE YOUR IPCOP DISK BEFORE AND TRY ON THAT COPY !
vi /root/.gnupg/gpg.conf allow-non-selfsigned-uid
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.11 (GNU/Linux) mQGiBE6tl4URBADaTe725TiF3pyzIKjwarWGbvHBXY2zdvBGAdh+2tsivAPLUUhI r9O2yO7CxN6/CpIhUqv/evGYLg82DkEjIRcaV8BtoteQblXRIlDQrR+j7wQF2Zky 9my8Lb5Nxj3Yu83/3g/9KjZXPND5cMhuWqCZTC3558x0v+axOu1Hj7y/lwCgyypH NMxd6sQw9DpFmoJUhnHu1KUEALWaog20n3w6GQ2h2OISz8rsT1IS2Ilwyz57c6jC 5Bghfxemr/lT+oFoiEQc4bbjYE/AERwQzopv+ulWricOXKvSBUe3lMnzr2oz1aG+ F9RB8d2GwKUzoDs2Zrda1AEEZx6vfY9SGvowa0xlszA+ibXYCizLFeNlzyLrGcyy ZK9ABADN9Dg9hidJBqwiNKiCGD39w9joXnTdHiycIFVqR4BUgkEW1/Yo515keNgL cSzQNrOCFcHSF9eGNHjptsFUIpO0aNY1NnFNsx4R/zWCZDIUiCFSjAOs6neU6FNk f0bLqulFpMqMLYSx/oo4AeTZ8U7CtZlCH8QSjXhbiufZsCKwDLRURnJhbmNrIEJv dXJkb25uZWMgKGh0dHA6Ly9mcmFuY2s3OC5hdGguY3ggdXBkYXRlIGlwY29wIDEu NC54KSA8ZmJvdXJkb25uZWNAY2hlei5jb20+iGIEExECACIFAk6tl4UCGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEMAQog6Nr5t9CTIAnjvmG8MZk2hbZ/qo 2q5GAoJLY3fNAKCRNHRgAMsBN73H53gzO0RjZqO51A== =rHmh -----END PGP PUBLIC KEY BLOCK-----
gpg --import key.txt rm key.txt gpg --list-keys /root/.gnupg/pubring.gpg ------------------------ pub 1024D/4A3BFD9E 2003-10-03 uid IPCop Development Group (http://www.ipcop.org/) pub 1024D/8DAF9B7D 2011-10-30 uid Franck Bourdonnec (http://franck78.ath.cx update ipcop 1.4.x)
Translation howto
You need to have access to the IPCop console. The best way is to 'ssh' into it from your workstation. You have windows open for work and your browser to immediately test the result on the GUI.
IPCop is delivered with 'Vim' as editor. If you are not confident with it, learn it or install Midnight Commander. It provides a simple easy to use editor as well as a good way to walk through IPCop's architecture. I think an addon exists. Ask google!
The language files are located in /var/ipcop/langs. You will find one for every language available on IPCop. These files are for the GUI only. The installer/setup programs use another system. IPCop uses a caching system to limit repetitive reading of language files. You must erase the cache files if you want to see your work: rm /var/run/cache*. Theses files are reconstructed at IPCop startup and IPCop patch application.
The basic principal used by IPCop is merging the en.pl file into the used language file. Because en.pl contains the complete set of translations, IPCop is allways able to display something. It can give strange results, mixing English and native language when translations are incomplete.
| en.pl | fr.pl |
|---|---|
%tr = ( %tr, 'action' => 'Action', 'add' => 'Add', 'add a host' => 'Add a host:', 'add a new rule' => 'Add a new rule:', 'add device' => 'Add device', 'add network' => 'Add network', ); |
%tr = ( %tr, 'action' => 'Action', 'add' => 'Ajouter', 'add a host' => 'Ajouter un hôte:' 'add device' => 'Ajoute un Client Réseau' 'add network' => 'Ajouter un réseau' ); |
The syntax is quite simple: 'key' => 'text',
but if you misse a quote, failure is immediate: perl cannot read the file.
You can see the french file is incomplete. The key 'add a new rule' is absent, therefore the English text will be used.
All you have to do is use the search function in your editor to copy missing keys from en.pl and paste them in your .pl file.
You don't have to sort the keys, just add your work at the end of the file. You can also correct translations that hav
mistakes.
It is not easy to find missing keys just by looking at the .pl file. A small perl utility does that. Just copy it into the /var/ipcop/langs directory. Remember to check often the results on the GUI (refresh). When you are OK or have done something interesting, send me the .pl file, I will merge it into the existing database.
From time to time, we add some new keys or you see small typos. For limited operations, it is possible to work directly on the database. For this, you need to have an account. The person responsible for this is Harry Goldschmitt. Ask him for a username and password if you want to regularly participate on the IPCop project. Guides also need translation.
| Addon and blacklist | ||
|---|---|---|
| home (slow) | mirror (faster) | control |
| 1.4.2a | 1.4.2a | md5 |
| 1.4.1c | 1.4.1c | md5 |
| French 1,2,3,4 |
| English 1,2,3,4,5 |
| Deutsch 1,2,3,4 |
| Dutch |
| Russian |
| Chineese |
| Italian 1,2,3,4 |
For testing only, you can download the cdrom image of the next release of IPCop. This corresponds to a full build from the CVS. Up to date depends on CVS changes since my last full build. I don't rebuild for cosmetics updates ;-) You must replace this version when offical IPCop release is out! Don't forget to report if you are testing a particular point.
Date 2008; NOTHING NEW md5sum:
| français | english | deutsch |
| dutch | russian | italian |
| portuguese | chineese traditional | chineese simplified |
![]() |
AWStatS Last edit: may-18-2011 |