Hello.
When in the avelsieve section of the User Interface, I have some strings
in german, others not. The strings exist in the .po file so I think it's a
bug.
Example:
Beschreibung der Regel (Anzeigen als kurz tech source)
1 Wenn the header "From" beeinhaltet "welz (AT) fixe-post (DOT) de",
dann behalten.
2 Wenn the header "From" beeinhaltet "welz (AT) fixe-post (DOT) de",
dann file it
into the folder INBX.1_Privat. Then STP processing rules.
Action for Selected Rules:
"Enable" "Disable"
"L"
Cold someone confirm that before I write the bugfix, please.
Maybe it's just my setup which has gone awry.
Thanks,
Robert Welz

Sun, 2006-01-15 at 13:22 +0100, R. Welz wrote:

When in the avelsieve section of the User Interface, I have some strings
in german, others not. The strings exist in the .po file so I think it's a
bug.

Indeed it exists.

Has this happened after an upgrade of avelsieve? Try restarting the
apache server, and check it it still happens.

Alexandros Vellis wrote:
Sun, 2006-01-15 at 13:22 +0100, R. Welz wrote:
>
>When in the avelsieve section of the User Interface, I have some strings
>in german, others not. The strings exist in the .po file so I think it's
>a
>bug.
>
Indeed it exists.

Has this happened after an upgrade of avelsieve? Try restarting the
apache server, and check it it still happens.
It seems that hasn't compiled as
msgfmt -fo avelsieve.mo avelsieve.po.
The -f option was missing.

There are some spelling errors and some inconsistencies with the
translation itself, too. I will fix them without breaking the other
locales by inserting some new strings.

Where can I publish the bugfix then?

Thx,
Robert

This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DWNLAD SPLUNK!
865&op=click

Sun, 2006-01-15 at 15:34 +0100, R. Welz wrote:
It seems that hasn't compiled as
msgfmt -fo avelsieve.mo avelsieve.po.
The -f option was missing.

course. :/ It wouldn't be a good idea to enable -f though, because
they really need to be checked by a human eye.

There are some spelling errors and some inconsistencies with the
translation itself, too. I will fix them without breaking the other
locales by inserting some new strings.

Where can I publish the bugfix then?

Please do check the translation and remove fuzzy markers if the string
is ok. Just send the new .po file to me by email so that I will include
it in the next release.

>

Alexandros Vellis wrote:
>
>Sun, 2006-01-15 at 13:22 +0100, R. Welz wrote:
>>
>>
When in the avelsieve section of the User Interface, I have some
strings in german, others not. The strings exist in the .po file so I
think it's a bug.
>>
>Indeed it exists.
>>
>>
>Has this happened after an upgrade of avelsieve? Try restarting the
>apache server, and check it it still happens.
It seems that hasn't compiled as
msgfmt -fo avelsieve.mo avelsieve.po. The -f option was missing.
-f option triggers use of fuzzy translations. Fuzzy translations are not
supposed to be used. They are not confirmed by translator. If you have
avelsieve.po with fuzzy translations (msgfmt -o /dev/null
avelsieve.po), fix them.

There are some spelling errors and some inconsistencies with the
translation itself, too. I will fix them without breaking the other
locales by inserting some new strings.

You are not supposed to fix things by adding new strings. Gettext has
msgmerge and xgettext utilities for that.

This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DWNLAD SPLUNK!

Alexandros Vellis wrote:
Sun, 2006-01-15 at 15:34 +0100, R. Welz wrote:
>It seems that hasn't compiled as
>msgfmt -fo avelsieve.mo avelsieve.po.
>The -f option was missing.
>
course. :/ It wouldn't be a good idea to enable -f though, because
they really need to be checked by a human eye.
>
>
>There are some spelling errors and some inconsistencies with the
translation itself, too. I will fix them without breaking the other
locales by inserting some new strings.
>Where can I publish the bugfix then?
>
Please do check the translation and remove fuzzy markers if the string
is ok. Just send the new .po file to me by email so that I will include
it in the next release.
--

Tomas Kuliavas wrote:
>>
>
>Alexandros Vellis wrote:

You are not supposed to fix things by adding new strings. Gettext has
msgmerge and xgettext utilities for that.

No. Yast hasn't. What do I miss here?

Robert

Tomas Kuliavas wrote:
>>
>
>Alexandros Vellis wrote:
>>
Sun, 2006-01-15 at 13:22 +0100, R. Welz wrote:

When in the avelsieve section of the User Interface, I have some
strings in german, others not. The strings exist in the .po file so I
think it's a bug.

Indeed it exists.

Has this happened after an upgrade of avelsieve? Try restarting the
apache server, and check it it still happens.
>It seems that hasn't compiled
>as
>msgfmt -fo avelsieve.mo avelsieve.po. The -f option was missing.
>
-f option triggers use of fuzzy translations. Fuzzy translations are not
supposed to be used. They are not confirmed by translator. If you have
avelsieve.po with fuzzy translations (msgfmt -o /dev/null
avelsieve.po), fix them.
>
>There are some spelling errors and some inconsistencies with the
>translation itself, too. I will fix them without breaking the other
>locales by inserting some new strings.
>
You are not supposed to fix things by adding new strings. Gettext has
msgmerge and xgettext utilities for that.

My Mac has it. If I understand the man page correctly, msgmerge is for
overwriting old strings with new strings from a new .po file. No way to
insert new strings. What do I do then If I have to take an old string and
break it into two parts? I left the old string for compatibility with the
other locales Thgis part is nonsense. Since I changed the sourcecode
the other locales will break anyway. So what do I do now?

Robert

When in the avelsieve section of the User Interface, I have some
strings in german, others not. The strings exist in the .po file
so I think it's a bug.

Indeed it exists.

Has this happened after an upgrade of avelsieve? Try restarting the
apache server, and check it it still happens.
It seems that hasn't
compiled as msgfmt -fo avelsieve.mo avelsieve.po. The -f option was
missing.
>>
>-f option triggers use of fuzzy translations. Fuzzy translations are
>not supposed to be used. They are not confirmed by translator. If you
>have avelsieve.po with fuzzy translations (msgfmt -o
>/dev/null
>avelsieve.po), fix them.
>>
There are some spelling errors and some inconsistencies with the
translation itself, too. I will fix them without breaking the other
locales by inserting some new strings.
>>
>You are not supposed to fix things by adding new strings. Gettext has
>msgmerge and xgettext utilities for that.
>
My Mac has it. If I understand the man page correctly, msgmerge is
for overwriting old strings with new strings from a new .po file. No way
to insert new strings. What do I do then If I have to take an old string
and break it into two parts? I left the old string for compatibility with
the other locales Thgis part is nonsense. Since I changed the
sourcecode the other locales will break anyway. So what do I do now?

Robert

Extract updated strings with xgettext, merge your translation with updated
avelsieve.pot file, translate updated file.

cd /sm-path/plugins/avelsieve/po
/xgetpo
/mergepoall

edit updated avelsieve.po file.

Manually editing gettext translation files with plain text editors is
inefficient and prone to errors.

When I create a new rule matching the "envelope" I get the following error
from Cyrus:

Unable to load script to server.
Server responded with:
script errors:
line 11: envelope not require
Please contact your administrator.

Why is this and is that configurable on Cyrus and how can I deaktivate the
"envelope-rule" functionality of squirrel mail.

Thx,
Robert

(only 4 fuzzies left, I will do the Spamrules futties now ;)

Sun, 2006-01-15 at 18:15 +0100, R. Welz wrote:

Unable to load script to server.
Server responded with:
script errors:
line 11: envelope not require
Please contact your administrator.

, forgot to add the proper capability "require".

Try the attached quick fix. I will try to test it tomorrow, and release
a new version soon as well.

Alexandros Vellis wrote:
Sun, 2006-01-15 at 18:15 +0100, R. Welz wrote:
>
>Unable to load script to server.
>Server responded with:
>script errors:
>line 11: envelope not require
>Please contact your administrator.
>
, forgot to add the proper capability "require".

And where are the Spamrule Actions? I see only "Discard" but there ought
to be Junk Folder and Trash Folder as well , as far as I can see from the
translation?

Greetings,
Robert

This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DWNLAD SPLUNK!
865&op=click