Re: [SM-PLUGINS] Plugin development perplexity

Thx for the clear words Paul.

I have to accept your decision and I'll quit squirrelmail universe immediately.

Thx you all for a good time!

Live long and prosper
Florian

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--

-- 
squirrelmail-i18n mailing list
Posting guidelines: http://squirrelmail.org/wiki/MailingListPostingGuidelines
Information about translations:
http://www.squirrelmail.org/wiki/LanguageTranslation
List address: squirrelmail-i18n <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (Subscribe/Unsubscribe/Change options): 
https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n

Japanese Input translations

Hello,

  As I will be releasing an updated version of the Japanese Input
plugin, here are the tanslations for it to be committed to the SM
translations.

Thank you,
Paul

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

--

-- 
squirrelmail-i18n mailing list
Posting guidelines: http://squirrelmail.org/wiki/MailingListPostingGuidelines
Information about translations:
http://www.squirrelmail.org/wiki/LanguageTranslation
List address: squirrelmail-i18n <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (Subscribe/Unsubscribe/Change options): 
https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n

Re: Japanese Input translations

> As I will be releasing an updated version of the Japanese Input
> plugin, here are the tanslations for it to be committed to the SM
> translations.

Ferdie Ferdsen's translation is already in the repository, so I'm keeping
that one.

Sincerely,
Fredrik

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--

-- 
squirrelmail-i18n mailing list
Posting guidelines: http://squirrelmail.org/wiki/MailingListPostingGuidelines
Information about translations:
http://www.squirrelmail.org/wiki/LanguageTranslation
List address: squirrelmail-i18n <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (Subscribe/Unsubscribe/Change options): 
https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n

Re: Japanese Input translations

On 2/4/07, Fredrik Jervfors <jervfors <at> squirrelmail.org> wrote:
> > As I will be releasing an updated version of the Japanese Input
> > plugin, here are the tanslations for it to be committed to the SM
> > translations.
>
> Ferdie Ferdsen's translation is already in the repository, so I'm keeping
> that one.

Thank you

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--

-- 
squirrelmail-i18n mailing list
Posting guidelines: http://squirrelmail.org/wiki/MailingListPostingGuidelines
Information about translations:
http://www.squirrelmail.org/wiki/LanguageTranslation
List address: squirrelmail-i18n <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (Subscribe/Unsubscribe/Change options): 
https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n

Re: [SM-PLUGINS] Plugin development perplexity

Hello Florian,

Sorry to hear you quit the SquirrelMail universe.

If you read the mail from Paul carefully then you also could read:

Quote Paul:
"Now as for losing you around these parts: as I have already said, the
fact that you seem to have time and interest and ability to contribute
to the project is potentially very promising.  Based on those things
alone, we all welcome you with open arms and hope that you do not
leave.  Don't be mistaken about the usefulness of your patches,
either.  As I update the various plugins under my purview that you
have sent patches for, I will in fact consult them for any ideas I
don't already have."

Of course I understand that the rest of the message from Paul didn't suit
you but they had to be said and I support him in that.

SquirrelMail is very popular because of the plugins and the quality of it.
The only way to achieve that is using high plugin standards. Paul does a
very good job in keeping those standards high.

That requires leadership and a lot of patience in pointing plugin
developers in the right direction.

FOSS is a lot of things and that includes leadership and control. If you
cannot accept that then start your own FOSS project.
FWIW, leadership and control !== dictatorship. We always appreciate
discussions based on good argumentation and we are always open minded in

Squirrelmail and RFC 2047 ?

Hi,

I have come across the following issue which I don't know how to solve:

I reguarly receive mails in which the subject is Q-encoded (as per RFC 2047). 
Squirrelmail shows these subject lines in their encoded form instead of 
decoding them.
So I see
Subject:   	=?iso-8859-1?Q?Re: ASR 2.2.0?=

instead of
Subject:   	Re: ASR 2.2.0

I have tested this with Squirrelmail 1.4.5, 1.4.6 and 1.5.1. They all show the 
same behaviour.

Is there something wrong with my configuration or is this a known issue ?

Thanks.

Geert
--

-- 
Kobalt W.I.T.
Web & Information Technology
Brusselsesteenweg 152
1850 Grimbergen

Tel  : +32 479 339 655
Email: info <at> kobaltwit.be

Re: Squirrelmail and RFC 2047 ?

> I have come across the following issue which I don't know how to solve:
> 
> I reguarly receive mails in which the subject is Q-encoded (as per RFC 2047). 
> Squirrelmail shows these subject lines in their encoded form instead of 
> decoding them.
> So I see
> Subject:   	=?iso-8859-1?Q?Re: ASR 2.2.0?=
> 
> instead of
> Subject:   	Re: ASR 2.2.0
> 
> I have tested this with Squirrelmail 1.4.5, 1.4.6 and 1.5.1. They all show the 
> same behaviour.
> 
> Is there something wrong with my configuration or is this a known issue ?

rfc 2047, 2. Syntax of encoded-words

----
IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's
by an RFC 822 parser.  As a consequence, unencoded white space
characters (such as SPACE and HTAB) are FORBIDDEN within an
'encoded-word'. 
----

space must be encoded.

--

-- 
Tomas

Re: Squirrelmail and RFC 2047 ?

On Wed, February 14, 2007 20:33, Tomas Kuliavas wrote:
> ----
> IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's
> by an RFC 822 parser.  As a consequence, unencoded white space
> characters (such as SPACE and HTAB) are FORBIDDEN within an
> 'encoded-word'.
> ----
>
> space must be encoded.

Hmm. Would there be a technical problem with allowing the space in our
case? Just to be liberal with what we accept? Or is there a drawback in
doing that?

Thijs

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--

-- 
squirrelmail-i18n mailing list
Posting guidelines: http://squirrelmail.org/wiki/MailingListPostingGuidelines
Information about translations:
http://www.squirrelmail.org/wiki/LanguageTranslation
List address: squirrelmail-i18n <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (Subscribe/Unsubscribe/Change options): 
https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n

Re: Squirrelmail and RFC 2047 ?

On Wed, 2007-02-14 at 18:13 +0100, Geert Janssens wrote:
> So I see
> Subject:   	=?iso-8859-1?Q?Re: ASR 2.2.0?=
> 
> instead of
> Subject:   	Re: ASR 2.2.0

I've checked this out with other clients. The only client that supported
it was Thunderbird. All others displayed this the same as SquirrelMail,
i.e. the top one.

I therefore think that fixing the sender of that string is a much better
strategy than fixing all clients. It's not that SquirrelMail is the only
one being picky here.

What mailer is sending those headers?

Thijs

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--

-- 
squirrelmail-i18n mailing list
Posting guidelines: http://squirrelmail.org/wiki/MailingListPostingGuidelines
Information about translations:
http://www.squirrelmail.org/wiki/LanguageTranslation
List address: squirrelmail-i18n <at> lists.sourceforge.net

Re: Squirrelmail and RFC 2047 ?

Thijs Kinkhorst <kink <at> squirrelmail.org> writes:

> 
> On Wed, February 14, 2007 20:33, Tomas Kuliavas wrote:
> > ----
> > IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's
> > by an RFC 822 parser.  As a consequence, unencoded white space
> > characters (such as SPACE and HTAB) are FORBIDDEN within an
> > 'encoded-word'.
> > ----
> >
> > space must be encoded.
> 
> Hmm. Would there be a technical problem with allowing the space in our
> case? Just to be liberal with what we accept? Or is there a drawback in
> doing that?

rfc 2047.

6.3. Mail reader handling of incorrectly formed 'encoded-word's

It is possible that an 'encoded-word' that is legal according to the
syntax defined in section 2, is incorrectly formed according to the
rules for the encoding being used.   For example:

(1) An 'encoded-word' which contains characters which are not legal
    for a particular encoding (for example, a "-" in the "B"
    encoding, or a SPACE or HTAB in either the "B" or "Q" encoding),
    is incorrectly formed.