All,
The Vadmin plugin has had some big changes made to it. The code has
been branched into a version 3.0, which, amongst many smaller
improvements, includes support for configurable backends -- currently a
SQL backend (as well as the traditional VMailMgr backend) is included.
Also, it is now more extensible, which means that it is more suited as a
full-blown control panel system.
No releases are yet available (although I am willing to send a release
package offlist), but you can get the code from anonymous CVS here:
The code is fairly stable (beta quality at least IM), but that's just
here; so we'll officially say it's still very much in the alpha stage.
Early adopters' comments and testing always appreciated.
-paul
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast.

debian (AT) qv90 (DOT) de wrote:
Hi All,

here a plugin patch to "abook_import_export" 0.9 to support german
translation.

Thanks, but:

- don't include binary files in diff (.mo) (drop a option from diff
command)
- locale placement was correct before your patch: instead, the
translation file needs to go in the core locale directory and you need
to send you po file to the i18n list; no patch is required for the plugin
-paul

SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast.

>

Thanks, but:

- don't include binary files in diff (.mo) (drop a option from diff
command)
- locale placement was correct before your patch: instead, the
translation file needs to go in the core locale directory and you need
to send you po file to the i18n list; no patch is required for the plugin

-paul

Hi Paul,
sorry for including .mo file, BUT take a look at the other
modifications. there are some code modifications which I have to add to
get the desired translation

Jam

SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast.

debian (AT) qv90 (DOT) de wrote:
>>
Thanks, but:

>- don't include binary files in diff (.mo) (drop a option from diff
>>command)
>- locale placement was correct before your patch: instead, the
>>translation file needs to go in the core locale directory and you need
>>to send you po file to the i18n list; no patch is required for the plugin
>>
paul

Hi Paul,
sorry for including .mo file, BUT take a look at the other
modifications. there are some code modifications which I have to add to
get the desired translation

I *did* read them. Did you read MY email? That's what my 2nd bullet
was about. Please read my email again and actually try what I am
telling you.

-paul

SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast.

PGP SIGNED MESSAGE
Hash: SHA1

Hi All,
--
here a plugin patch to "abook_import_export" 0.9 to support german
translation.

from German translation file
-
# SME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S CPYRIGHT HLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSIN\n"
"Report-Msgid-Bugs-To: \n"
"PT-Creation-Date: 2005-06-13 09:54+0200\n"
"PRevision-Date: YEAR-MDA H:MI+ZNE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL (AT) li (DOT) org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=IS\n"
"Content-Transfer-Encoding: 8bit\n"
-

can you fix translation header and comments?

header should not have fuzzy mark. Header fields should not contain
default values. comments section should contain copyright holder and not
default comment.

check file with 'msgfmt -v -c -o /dev/null abook_import_export.po' command
before you submit it.

For example
-
# Lithuanian Translation of SquirrelMail abook_import_export plugin.
# Copyright (c) 2005 The SquirrelMail Project Team
# Tomas Kuliavas <tokul (AT) users (DOT) sourceforge.net>, 2005.
# $Id: abook_import_export.po,v 1.1 2005/06/10 11:04:35 tokul Exp $
msgid ""
msgstr ""
"Project-Id-Version: abook_import_export 0.9\n"
"Report-Msgid-Bugs-To: \n"
"PT-Creation-Date: 2005-03-16 13:25+0200\n"
"PRevision-Date: 2005-06-10 14:02+0300\n"
"Last-Translator: Tomas Kuliavas <tokul (AT) users (DOT) sourceforge.net>\n"
"Language-Team: Lithuanian <squirrelmail-i18n (AT) lists (DOT) sourceforge.net>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-

- --
Tomas
PGP SIGNATURE
Version: GnuPG v1.2.1 (GNU/Linux)

aqUAoK1lZUuqQIW6CRTNVyDtW1EF
=Fzn6
PGP SIGNATURE

SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast.

$v->sname -_($v->sname) is not acceptable.

You are using dynamic string in gettext call. I think address book names
are initialized during addressbook_init() function call. You only have to
switch to correct domain. See attached patch.

Sorry, but in my installation I have to translate that text, since it else
appears in English. I found no other solution for that problem (may it's a
1.4.4 core prob).

Change of locale directory is not acceptable.
Again sorry for the confusion. I only followed the mandatory guidelines in
Chapter

"Internationalization" shows up with:
3. Finally, you just need to create your own locale. You should create
a directory structure like this in the plugin directory:

From INSTALL file
-
Plugin translations use abook_import_export domain.
abook_import_export.po and abook_import_export.mo files should be
stored in same directory that stores squirrelmail.po and
squirrelmail.mo files. Translations are maintained by SquirrelMail
Internationalization Team and are distributed in SquirrelMail locale
packages.
-

Seems a bit confusing to hand out mandatory guidelines (a couple of
plugins follows those guidelines) and then step back and tell me
translations has to be stored in SM locale :-)

Please apologize, I don't wanted to cross someone.
Jam

SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast.

Thu, July 21, 2005 3:37 pm, Paul Lesneiwski wrote:
All,
--
The Vadmin plugin has had some big changes made to it. The code has
been branched into a version 3.0, which, amongst many smaller improvements, includes
support for configurable backends -- currently a SQL backend (as well as the traditional
VMailMgr backend) is included.
Also, it is now more extensible, which means that it is more suited as a
full-blown control panel system.

No releases are yet available (although I am willing to send a release
package offlist), but you can get the code from anonymous CVS here:

--
The code is fairly stable (beta quality at least IM), but that's just
here; so we'll officially say it's still very much in the alpha stage.

Early adopters' comments and testing always appreciated.
--
-paul

Thanks Paul,
I have been waiting for just such a thing.

A first comment: When enabled the plugin causes the following error when attempting to
login.
FATAL ERRR: vadmin config file '/plugins/vadmin/conf/.conf' does not exist.

naming it '.conf' gets me past that.

But now I need to figure out what to do about:

Warning:
vadmin_prep(/):
failed to open stream: No such file or directory in
/ on line 32

Warning: vadmin_prep(): Failed opening
'/' for inclusion
(include_path='.:/usr/lib/php') in
/ on line 32

Fatal error: Call to undefined function: vadmin_getvar() in
/ on line 38

I do not need *any* (that I know of) of the vmailmgr functionality as all I wish to have
is a frontend plugin for creating new users, forwards, and aliases into mysql databases.

Thanks,
Charles Andrews

SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. 492&op=click

>>Change of locale directory is not acceptable.

Again sorry for the confusion. I only followed the mandatory guidelines in
Chapter

"Internationalization" shows up with:
3. Finally, you just need to create your own locale. You should create
a directory structure like this in the plugin directory:


>>From INSTALL file

>>Plugin translations use abook_import_export domain.
>>abook_import_export.po and abook_import_export.mo files should be
>>stored in same directory that stores squirrelmail.po and
>>squirrelmail.mo files. Translations are maintained by SquirrelMail
>>Internationalization Team and are distributed in SquirrelMail locale
>>packages.

>>

Seems a bit confusing to hand out mandatory guidelines (a couple of
plugins follows those guidelines) and then step back and tell me
translations has to be stored in SM locale :-)

We'll update that in the docs. Thank you for reading it that closely.
We are migrating away from individual plugin locale directories.

- paul

SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast.