[feladat @ 84] Bugfix. The function zone_count() now also counts zones an owner has only partial access to, not just those zones the owner has full access to. This fixes just the count, the zones a user has partial access to are not (yet!) shown in the "list zones" page. Bugfix. In the zone listing the "edit" button is now show for users with access level 1. Untill now they were presented an overview of the zones they could change, but there was no link for them to actually edit the zone. Bugfix. Some of the buttons in the "edit zone" interface that are of no use to a user with access level 1 have been hidden. Bugfix. Make sure a user with access level 1 with only partial access to a zone cannot add new records to that zone. Only the zone owner should be able to add new record. Bugfix. If a user with access level 1 edits a record in a zone he has only partial access to, an error was shown because of call to a non- existing function in the PEAR:MDB2. This bug was most likely introduced while migrating from PEAR:DB to PEAR:MDB2. Bugfix. A user with access level 1 was able to delete all records of a zone he has only partial access to. Some additional checks have been added. Bugfix. If a user with accees level 1 has partial access to one or more zones starting with a certain character, but did not own at least one entire zone starting with the same character, the character wasn't clickable in the "list zone" page. Interface. If no record or zone id is given for delete_record.php or delete_domain.php, don't just die but echo a nice message. The i18n files have not yet been updated to reflect this change. Interface. If no master IP is given in delete_supermaster.php, don't just die but echo a nice message. The i18n files have not yet been updated to reflect this change. [All fixes by Peter Beernink.]

     1

README.i18n

     2

     3

     4

Using a translation

     5

-----------------------------------------------------------------------

     6

     7

All available translations can be found in the locale directory in the

     8

poweradmin base directory. The Dutch translation for example, can be

     9

found in locale/nl_NL. To review the status of the translation, you 

    10

can have a look at the nl.po file in the LC_MESSAGE directory.

    11

    12

If you want to use a translation, say the nl_NL, all you have to do is 

    13

edit inc/i18n.php file and change the $language variable to the desired

    14

language, for example "nl_NL".

    15

    16

If this doesn't work, please try to do the following:

    17

    18

 - cd /path/to/poweradmin/locale/$lang/LC_MESSAGES/

    19

 - msgfmt $lang.po -o message.mo 

    20

    21

If that doesn't help either, most likely your system itself is not

    22

setup properly. See <https://rejo.zenger.nl/misc/1176630442.php> maybe

    23

of some help.

    24

    25

    26

Adding a new translation

    27

-----------------------------------------------------------------------

    28

    29

If you want to create a new translation you can do the following. For

    30

example, if you want to create a Dutch translation:

    31

    32

 - cd /path/to/poweradmin/

    33

 - mkdir -p locale/nl_NL/LC_MESSAGES/

    34

 - cp docs/template.pot locale/nl_NL/LC_MESSAGES/nl.po

    35

 - cd locale/nl_NL/LC_MESSAGES/

    36

 - vim nl.po

    37

 - msgfmt nl.po -o message.mo

    38

    39

    40

Updating the translation template file

    41

-----------------------------------------------------------------------

    42

    43

If creating a new translation and you are not sure if the template file

    44

that was provided in the distribution, you may want to re-create the 

    45

template file. To do so, do the following:

    46

    47

    48

 - cd /path/to/poweradmin/

    49

 - xgettext --no-wrap -o docs/template.pot *.php inc/*.php

    50

    51

The last command updates the template file in docs/ directory.

    52

    53