[Mailman-Developers] Possible re-design for the cause of internationalization
Tomas Fasth
tomas@euronetics.se
Fri, 4 Sep 1998 06:03:12 +0200
This is a multi-part message in MIME format.
------=_NextPart_000_0147_01BDD7C9.B3155540
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi, I'm the guy trying to translate Mailman to Swedish.
Currently the task of doing a translation is managable but very time =
consuming. Further, since it involves editing code files it sure makes =
you feel insecure about it. It also complicates the task of having the =
code up to date with the main (american english) trunk although CVS can =
do a good job to make that task less painful.
Anyway, in order to avoid chaos in localized installations, there seem =
to be a need to change the scheme of how to incorporate language =
specific text in user presentations. There has already been some =
postings about that.
Unfortunately, using the "patch" approach will probably make the code =
look "messy" and less readable. Therefore it might be a good idea to do =
a re-design of the current text generation part of the code in Mailman.
The question is, what is the proper procedure to achieve this?
Is there currently an "architect" for Mailman?
Is that person willing to coordinate such an efford?
If a CVS branch is created for this purpose, how do you earn check-in =
permission for that branch?
Is there anybody out there who cares about this matter part from me (if =
not, why bother)?
Tomas
------=_NextPart_000_0147_01BDD7C9.B3155540
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Hi, I'm the guy trying to translate =
Mailman to=20
Swedish.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT><FONT size=3D2></FONT><FONT =
color=3D#000000=20
size=3D2>Currently the task of doing a translation is managable but very =
time=20
consuming. Further, since it involves editing code files it sure makes =
you feel=20
insecure about it. It also complicates the task of having the code up to =
date=20
with the main (american english) trunk although CVS can do a good job to =
make=20
that task less painful.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT><FONT size=3D2></FONT><FONT =
color=3D#000000=20
size=3D2>Anyway, in order to avoid chaos in localized installations, =
there seem to=20
be a need to change the scheme of how to incorporate language specific =
text in=20
user presentations. There has already been some postings about=20
that.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>Unfortunately, using the =
"patch"=20
approach will probably make the code look "messy" and less =
readable.=20
Therefore it might be a good idea to do a re-design of the current text=20
generation part of the code in Mailman.</FONT></DIV>
<DIV><FONT size=3D2>The question is, what is the proper procedure to =
achieve=20
this?</FONT></DIV>
<DIV><FONT size=3D2>Is there currently an "architect" for=20
Mailman?</FONT></DIV>
<DIV><FONT size=3D2>Is that person willing to coordinate such an=20
efford?</FONT></DIV>
<DIV><FONT size=3D2>If a CVS branch is created for this purpose, =
h</FONT><FONT=20
size=3D2>ow do you earn check-in permission for that =
branch?</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Is there anybody out there who cares about this =
matter part=20
from me (if not, why bother)?</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Tomas</FONT></DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_0147_01BDD7C9.B3155540--