Hello anybody,
Here are up-to-date (yesterdays) translations in French. If anyone
interested...
Another question: will managesieve patch from Aleksander 'A.L.E.C'
Machniak (alec/at/alec/dot/pl) be incorporated before v0.2 ?
Thank you for this great webmail !
--
Geoffroy DESVERNAY
-----
99, av. des Chartreux
13004 MARSEILLE
-----
Tel: 04 91 62 73 90
Mail: dgeo(a)dgeos.net
--- 8< --- detachments --- 8< ---
The following attachments have been detached and are available for viewing.
http://detached.gigo.com/rc/5C/asYyFDfy/messages.inchttp://detached.gigo.com/rc/5C/asYyFDfy/labels.inchttp://detached.gigo.com/rc/5C/asYyFDfy/signature.asc
Only click these links if you trust the sender, as well as this message.
--- 8< --- detachments --- 8< ---
_______________________________________________
List info: http://lists.roundcube.net/dev/
Sometimes it's good to give changes some time. :) It's working! After
logging in today the send as new function is working. I've attached the
patch. What's missing is a translation and new button images (I copied the
forward buttons). I can do the translation stuff but not the buttons.
Btw: Roundcube is a very good webmail package.
Regards
Christian
On 25-Oct-2008 23:48:32, Christian Beer wrote:
Hi folks,
one of my customers requested a feature that is available in thunderbird.
It's called "send as new mail" there. I figured out that it should be easy
to add to roundcube. I used the forward command as a template and tried to
add a new command on my own. But it's not working as intended. The command
button is shown but it's disabled in all cases. I expected that it is
available when the forward command is available, but it's not. I've changed
the files program/steps/mail/compose.inc, program/js/apps.js,
skins/default/templates/mail.html and
skins/default/templates/message.html.
I can provide the diffs to version 0.2-beta if needed. Does anyone has an
idea where to change the code in order to get this extra function working?
Regards
Christian
--- 8< --- detachments --- 8< ---
The following attachments have been detached and are available for viewing.
http://detached.gigo.com/rc/4y/TkgCMY5a/compose-as-new.diff
Only click these links if you trust the sender, as well as this message.
--- 8< --- detachments --- 8< ---
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hi folks,
one of my customers requested a feature that is available in thunderbird.
It's called "send as new mail" there. I figured out that it should be easy
to add to roundcube. I used the forward command as a template and tried to
add a new command on my own. But it's not working as intended. The command
button is shown but it's disabled in all cases. I expected that it is
available when the forward command is available, but it's not. I've changed
the files program/steps/mail/compose.inc, program/js/apps.js,
skins/default/templates/mail.html and skins/default/templates/message.html.
I can provide the diffs to version 0.2-beta if needed. Does anyone has an
idea where to change the code in order to get this extra function working?
Regards
Christian
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hey all,
I ran into a problem in the way RoundCube handles mail messages with
"Date:" headers that aren't 100% compliant with RFC 2822's date format.
The header in question is:
Date: Tue, 21 Oct 2008 00:13:54 0600
Notice that the time zone offset specifier is missing the "+/-" prefix.
Thunderbird seems to drop the zone offset in this case and assume it's a
local date. RoundCube, on the other hand, passes it into PHP's handy
"strtotime" function which interprets 0600 as the year. This leads at
the very least to display problems (in the message list and the message
display), and worst case to invalid dates in the database if caching is
enabled.
I'd like to make RoundCube a little more tolerant, so I was wondering
what everyone else thought about possible solutions. The options I'm
considering are:
1. Parse the date using a fixed format string (e.g. "D, d M Y H:i:s
O") and one of PHP's other date functions. This would prevent
misinterpretation but might be even less tolerant.
2. Analyze the string before passing to strtotime() to identify and
work around known issues (of which there would be exactly one at
this point). This is a single special case kind of solution, but
strtotime might be reliable enough that this is the only case
we'll hit.
3. Find a 3rd party RFC2822-compliant PHP date parser library.
What do you all think?
--
*Eric Stadtherr*
estadtherr(a)gmail.com <mailto:estadtherr@gmail.com>
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hello,
It has been suggested to use .po files for translation. This may be a
viable path, but it may introduce unneeded complexity.
My real concern is about semantic changes in translatable strings. For
example, if en_US 'foo' has "Do bar" as a string and then later changed
to "Do baz", all other translations are left unchanged, because the
online translator does not detect the change in meaning.
To combat this, an original en_US string may be added as a comment after
the translated string.
Examle.
in en_US:
$labels['changecolor']='Change color';
in en_GB:
$labels['changecolor']='Change colour';//Change color
After 'Change color' is changed to 'Change text color', translator
should offer to revise the translation in all locale files because the
comment in the locale file does not match the current en_US string.
--
Dennis
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hello,
I have updated the Russian translation. There are some refinements.
--
Dennis
--- 8< --- detachments --- 8< ---
The following attachments have been detached and are available for viewing.
http://detached.gigo.com/rc/yW/JEtR4sh6/ru_RU.patch
Only click these links if you trust the sender, as well as this message.
--- 8< --- detachments --- 8< ---
_______________________________________________
List info: http://lists.roundcube.net/dev/
When editing contacts, some invalid characters are not stripped or
handled in some way. They make it all the way to the sql statement
before things trip up. (Using a prepare statement thankfully prevents
injecting a second statement. More details in:
http://trac.roundcube.net/ticket/1485504)
I can work on a patch, but I'd appreciate some guidance first:
Should the backend explicitly validate the input against a regular
expression?
What is valid/invalid?
How should the interface report bad characters and/or failed contact
saves to the user?
Thanks,
Ziba
Webmaster Team
University of Michigan
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hello,
filled in the blanks in Finnish/Suomi labels.inc and messages.inc
Please find them in attachment.
T: Veljo Velling - W -
--- 8< --- detachments --- 8< ---
The following attachments have been detached and are available for viewing.
http://detached.gigo.com/rc/1N/OmS1pV1I/rc-finland-labels-me.zip
Only click these links if you trust the sender, as well as this message.
--- 8< --- detachments --- 8< ---
_______________________________________________
List info: http://lists.roundcube.net/dev/