the allowed categories and labels, and to
let the tools do their parsing according to their ability.
Jean-Christophe Helary
fun: http://mac4translators.blogspot.com
work: http://www.doublet.jp (ja/en fr)
tweets: http://twitter.com/brandelune
?
OmegaT or Virtaal both support TBX.
Jean-Christophe Helary
fun: http://mac4translators.blogspot.com
work: http://www.doublet.jp (ja/en fr)
tweets: http://twitter.com/brandelune
would be available from the Terminology
tab in OpenCTI.
What is the status of the migration Reiko mentioned ?
Jean-Christophe Helary
fun: http://mac4translators.blogspot.com
work: http://www.doublet.jp (ja/en fr)
tweets: http://twitter.com/brandelune
again.
I'll look for the next coordinator, but I'm not sure we will find to 3.3
transation.
Question.
So here is the question. What SUN or Oracle will/can offer for 3.3 JA
translation?
Thanks
-- Nakata Maho
Jean-Christophe Helary
fun: http
it to have shops in main European countries (like France and Germany)
that are at the forefront of OOo adoption in the world...
Jean-Christophe Helary
fun: http://mac4translators.blogspot.com
work: http://www.doublet.jp (ja/en fr)
tweets: http
On 16 mars 10, at 03:05, André Schnabel wrote:
For all who already tested the release candidate: you do not need to download
the editor again. The release version is exactly the same as the RC.
Hasn't the manual been slightly updated ?
Jean-Christophe Helary
-Christophe Helary (JA/EN FR)
http://mac4translators.blogspot.com/
http://twitter.com/brandelune
http://www.doublet.jp
-
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
how to make it start).
Jean-Christophe Helary
-
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
even
though the software does not seem to be super stable (I had 2 freezes
last night working with a real world XLIFF file).
It is also possible to work with OmegaT and Rainbow (both GPL/Java),
the process is much more robust.
Jean-Christophe Helary
. It may originate from a string
pasted from a Mac file into the code, or from something totally
different...
Jean-Christophe Helary
http://mac4translators.blogspot.com/
http://twitter.com/brandelune
;
Is it normal tags?
They seem to be carriage returns. CR. The line ending character for
Mac files.
Jean-Christophe Helary
-
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev
On 13 mars 08, at 15:15, Pavel Janík wrote:
Repeat after me: [...]
I am not sure this is the proper way to address fellow list members.
Why can't you accept that your proposal was not worded well enough to
gather enough support ?
Jean-Christophe Helary
their workflow is improved
with pootle/PO files and translate-toolkit magik but it is not the
case for a number of others.
Jean-Christophe Helary
http://mac4translators.blogspot.com
-Christophe Helary
http://mac4translators.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
category so that the purpose of each list is clearer ? Because
to me, everything about localization includes translation.
Jean-Christophe Helary
http://mac4translators.blogspot.com
pootle related) are discussed.
Jean-Christophe Helary
http://mac4translators.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
and translation related stuff...
But the thing is that we don't have any translation discussion here.
We have discussions about processes. Either processes on SUN side or
processes on team sides.
I don't think there is a clear cut between both.
Jean-Christophe Helary
encourage all the
teams that use OmegaT to work with the test version.
Jean-Christophe Helary
http://mac4translators.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
as a comment or is it
simply ignored ?
Jean-Christophe Helary
http://mac4translators.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.html
JC
On 3 mars 08, at 17:56, Aijin Kim wrote:
Hi JC,
In OmegeT 1.7.3, msgctxt seems to be simply ignored. There is no
display for msgctxt. What I meant was that OmegaT works ok with
'msgid' and 'msgstr' fields regardless of msgctxt field.
Regards,
Aijin
Jean-Christophe Helary 쓴 글
. It only sees msgid.
JC
Jean-Christophe Helary 쓴 글:
On 29 févr. 08, at 15:20, Aijin Kim wrote:
Hi JC,
I guess what Ain mentioned was that 'msgctxt' option during oo2po
saves the comment line in another field rather that adding to
msgid fileld. Then there won't be no change with msgid
and hide it from source string for
online translation. But not sure in terms of offline editors.
Since the string is a msgid it is handled as a source string and is
displayed as translatable.
Jean-Christophe Helary
http://mac4translators.blogspot.com
understand your comment. What Aijin asked is how does
OmegaT (and POedit, which I don't use) handle tweaked msgid.
My reply was that it handles them as normal msgid. I did not see a
reference to msgctxt.
Jean-Christophe Helary
http
:)
JC
Thanks,
Aijin
Jean-Christophe Helary wrote:
Hi all,
Some strings of po files have a line which was added to make each
msgid string be unique using --duplicates=msgid_comment option
during executing oo2po.
http://translate.sourceforge.net/wiki/toolkit/
duplicates_duplicatestyle
How can
that within OmegaT,
then merge the translated files to the original package :)
JC
On 25 févr. 08, at 16:41, F Wolff wrote:
Op Maandag 2008-02-25 skryf Jean-Christophe Helary:
Is it possible to only have the PO parts that need translation/
updating and not the whole set ?
All the already translated
before starting
the translations. That would make all the manipulations above
irrelevant.
JC
Even if there's no such a way, your workaround
will be a big help. Thank you again for your help!
Regards,
-Reiko
Jean-Christophe Helary wrote:
On 18 févr. 08, at 18:48, Jean-Christophe Helary
merge the translated data ?
Jean-Christophe Helary
http://mac4translators.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 18 févr. 08, at 18:48, Jean-Christophe Helary wrote:
Let me confirm. I understand the new/fuzzy is identified on OmegaT,
but once the translator did the translation and put the translated
string to the untranslated segment, how the reviewer can
recognize which one is the strings to review
?
It is not trivial.
The best way to work with OmegaT is to have untranslated files
(without fuzzies, those are handled separately by the TM matching
process), to translate them and to review them within OmegaT, or in a
plain text|PO editor.
Jean-Christophe Helary
http
Let me confirm. I understand the new/fuzzy is identified on OmegaT,
but once the translator did the translation and put the translated
string to the untranslated segment, how the reviewer can
recognize which one is the strings to review ?
Reiko,
PO is not exactly the strong point of OmegaT :)
of untranslated files will be, I guess, fully
handled offline, review included. But we still have to discuss that.
Sophie, Elsa, any comment ?
Jean-Christophe Helary
http://mac4translators.blogspot.com
escape rules depending on
the converter version defeats the purpose of TMXs... Do we need to
reconvert megabytes of file sets every time there is a new version of
TT ?
Jean-Christophe Helary
http://mac4translators.blogspot.com
with TMX created with previous TT versions ? Why do you think you have
the right to break our work because you suddenly decided to change
your specs ?
Jean-Christophe Helary
http://mac4translators.blogspot.com
-Christophe Helary
http://mac4translators.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I found a number of problems in the FR strings of Pootle. How is it
possible to correct them ?
Jean-Christophe Helary
http://mac4translators.blogspot.com/
-
To unsubscribe, e-mail
to
officially released Pootle.
Aijin
Jean-Christophe Helary 쓴 글:
On 3 févr. 08, at 22:17, Aijin Kim wrote:
Hi Jean-Christophe,
Sunvirtuallab Pootle only hosts OpenOffice.org and OpenSolaris.org.
Aijin,
On my project list I have:
Projects
OpenOffice.org HC2, OpenOffice.org UI
not match the real numbers I found when
actually opening the files.
Jean-Christophe Helary
http://mac4translators.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
strings, so the assumption that the listed values were strings and
not words was wrong from the beginning.
It seems to me both the word/string could should always be present
anywhere there is a count displayed to ensure that there is no
confusion possible.
Jean-Christophe Helary
-Christophe Helary
http://mac4translators.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
is translating PO files as text
files without regard for the PO file format, I don't think we can
lay the blame on the TMX specification or something else.
Are there PO parsers provided by GNU or GPLed that OmegaT could use to
improve its parsing of PO files ?
Jean-Christophe Helary
comprehensive.
Clytie,
I just tried it on my Mac and did not seem to have the problem you
describe. I use a /bin/ directory in my home folder, the directory is
in my PATH and gsicheck was called correctly by bash.
Jean-Christophe Helary
http
/universal TMX files.
Agreed, TMX depend on the original contents. And so it should be match
with the format in which the original contents is expressed.
... and that there is no truth on this, just opinions and systems
that work.
100% with you.
Jean-Christophe Helary
/ProjectMailingListList
On 27 déc. 07, at 23:49, Mechtilde wrote:
Hello,
after the second translation round I have had the idea to translate
also
the translation tool.
Jean-Christophe Helary
http://mac4translators.blogspot.com
in my
opinion.
Regarding Pootle, it is possible to upload the result after the
translation is completed ? If yes, you could translate based on SDF,
convert the result with oo2po and upload that to Pootle to ensure your
data is properly managed there ?
Jean-Christophe Helary
in a
practical way. Last but not least, such meta-information is mostly
useful for indetifying UI items, but for the whole rest of the
translation process (terminology management, style management etc) it
is simply useless.
Jean-Christophe Helary
http
in what I wrote.
We need a localization format (PO, XLIFF, key=value, anything) that
matches the localization data SUN provides us with (TMX). This has
nothing to with with developing or not developing the SDF format.
Jean-Christophe Helary
http
On 26 déc. 07, at 17:51, Alessandro Cattelan wrote:
Jean-Christophe Helary ha scritto:
What are the practical benefits related to using Pootle ?
Basically, I see two main benefits:
- it let's you assign files to translators so that you know who's
translating a given file;
- it provides
to protect the XML of
the translatable strings.
Jean-Christophe Helary
http://mac4translators.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
On 24 déc. 07, at 21:34, Yury Tarasievich wrote:
On Mon, 24 Dec 2007 11:29:59 +0200, Jean-Christophe Helary [EMAIL PROTECTED]
wrote:
Why has SUN moved from a workflow that ensures the most efficient use
of previous translations to a workflow that does not ?
Because it's
seen that what I wrote _did_ make sense.
Jean-Christophe Helary
http://mac4translators.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
, and what is your take on the fact that the TMX contents and the
SDF contents match but not the PO ? How do you think it is possible to
improve that so that translators can make better use of previously
translated strings ?
Because _that_ is what is being discussed...
Jean-Christophe
(Boris or anybody else, I Cc to OLT's dev list because that is
relevant here. How hard do you think it would be to have OLT's filters
work with OOo's l10n format: .sdf ?)
On 23 déc. 07, at 18:00, Yury Tarasievich wrote:
On Sun, 23 Dec 2007 05:59:05 +0200, Jean-Christophe Helary [EMAIL
need ant to build
OmegaT.
I hope this post will contribute to ease the OOo localization
process ! And I would like to thank Alex for the numerous test
versions he produced before _I_ was satisfied with sdf2txt !
Don't hesitate to ask questions if you have any !
Jean-Christophe Helary
that in OmegaT to benefit from the automatic TMX
matching functions
6) import the translated contents into the original
7) deliver a valid SDF file.
Anybody willing to test that before the translation really starts ?
Jean-Christophe Helary
On 28 nov. 07, at 19:55, Rafaella Braconi wrote:
Can anyone generate csv file from these tmx ?
I need the list of User Interface translation to use as the glossary
for OmegaT.
why don't you use the glossary available in Sun Gloss?
Is there a real equivalence between the UI files and Sun
On 28 nov. 07, at 19:21, Reiko Saito wrote:
Hi JC,
I understood your point.
To increase the leverage, we may be able to lower the lowest match-
rate,
or will use this tmx just for reference and search a certain string
as a file... what do you think ?
It is possible to use the sdf directly
On 27 nov. 07, at 22:49, Rafaella Braconi wrote:
Hi Reiko,
Reiko Saito ha scritto:
Hi Rafaella,
Exported stgings include English and translation, right ?
yes, that's correct.
Rafaella,
Would it be possible to have them exported to whatever format you like
before we get the files to
good use of
the data, as well as to propose better workflows in the future.
Jean-Christophe Helary
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 26 nov. 07, at 23:41, Rafaella Braconi wrote:
Hi Jean-Chrisophe,
an .sdf file can be opened and saved as CVS document...
Good, as Reiko just wrote, such contents would be interesting only it
it includes the English and the translation.
Can you confirm it is the case ?
Rafaella
On 26 nov. 07, at 15:17, Reiko Saito wrote:
Can the translator get the list of existing UI messages with
translation ?
The list formatted as csv, like
---
Expand Tree: ツリーを展開
Contact Tree: ツリーを収縮
If those files are available, any Translation Memory Editor, e.g.
OmegaT, can read the
localization is XLIFF.
And it would be even better if the XLIFF could be provided directly
from the original XML and not after a conversion to SDF, which
renders the whole process uselessly complex.
Jean-Christophe Helary
On Aug 11, 2007, at 8:02 PM, Clytie Siddall wrote:
So I'm not talking about converting between SDF, PO and XLIFF, or
between any combination of the three. I'm talking about using XLIFF
as the base translation format for OpenOffice.org.
This is what I suggested in a mail here at the
On 12 juil. 07, at 20:29, Jean-Christophe Helary wrote:
On 12 juil. 07, at 17:36, Rafaella Braconi wrote:
However, from what I understand here, the issue you see is not
necessarily Pootle but the format Pootle delivers which is .po. As
already said, Pootle will be able to deliver in near
.
And of course, this workflow is also valid for UI strings, since I
suppose they can also be converted to XML (if they are not already).
What about that ?
Jean-Christophe Helary (fr team)
-
To unsubscribe, e-mail: [EMAIL PROTECTED
On 13 juil. 07, at 10:42, ChengLin wrote:
HI,
We're trying to use OmegaT in Simplified Chinese Windows XP, it
can't save to UTF-8 but Chinese GBK.
Could anyone help us?
You go to Options/File Filter, select the file format you are using
and edit the output encoding.
Jean-Christophe
On 13 juil. 07, at 02:40, Alessandro Cattelan wrote:
Actually I haven't tried going through the procedure you described, I
think I'll give it a try with the next batch of files. We'll have
around
4,200 words to translate and as it is a reasonable volume, I think
I'll
have some time to
at launch and you'll be
translating in 15 mn. With a tool that professional translators use
everyday...
Jean-Christophe Helary (fr)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
there).
As long as OOo sticks to intermediate file formats (.sdf/.po/.xliff)
with the current unstable conversion processes, hack will be
necessary to reach the same level of efficiency other communities
have already reached. And _that_ is really too bad.
Cheers,
Jean-Christophe Helary
NetBeans manages its localization process.
Because we are loosing a _huge_ amount of human resources in the
current process.
Cheers,
Jean-Christophe Helary (fr team)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
through all the po loops that really don't provide much
more than yet another intermediate format that is anyway inconvenient
to translate.
JC
On 7 juil. 07, at 00:41, Jean-Christophe Helary wrote:
The reason why I tried to do that is because using the .po created
with oo2po along
The reason why I tried to do that is because using the .po created
with oo2po along with the TMX created with po2tmx does not work well.
The po2tmx removes data from escape sequences and that means more
things to type in the OmegaT edit window.
So, the idea was to consider the .sdf file as
Alessandro,
I have found a relatively painless way to directly translate the .sdf
files in OmegaT. I have to finish my part now so I'll document that
later.
JC
On 4 juil. 07, at 00:20, Alessandro Cattelan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
it seems that the PO
On 4 juil. 07, at 17:39, Arthur Buijs - ArtIeTee wrote:
Alessandro Cattelan schreef:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Christophe Helary ha scritto:
Alessandro,
I have found a relatively painless way to directly translate
the .sdf
files in OmegaT. I have to finish my part
On 19 juin 07, at 15:50, Alessandro Cattelan wrote:
Now I have one more question to which I'm sure Jean-Cristophe has the
answer... ;o)
When opening a project with OmegaT I thought that the text in
msgstr in
the PO file would show up in the target segment, but that is not the
case. I think
On 19 juin 07, at 18:17, Rafaella Braconi wrote:
Hi Alessandro, Jean-Christophe,
Alessandro Cattelan wrote:
Jean-Christophe Helary ha scritto:
I think Rafaella should be able to provide you with proper TMX files
that match the .sdf contents.
Rafaella has already provided us
OmegaT handles PO files pretty much as text files and thus does not
care about \, for it, the \ is just another character. Hence,
there is nothing that is generated by OmegaT in the screenshot I
showed. The files are displayed as they are.
Friedel,
I am not arguing for or against a certain
On 19 juin 07, at 17:12, Alessandro Cattelan wrote:
I don't understand why you need to create .pot instead of .po files. I
converted the sdf to po files and OmegaT just ignores the msgstr
content, so what is the use of having a pot file with empty msgstr
fields?
Because I am pretty sure
On 19 juin 07, at 19:51, Rafaella Braconi wrote:
yes, I was also suggesting jean-Christophe to use that tmx files
but I think that he really want to make sure to get the most
updated tmx files...
I am currently loading them and I don't see anything problematic.
Are you referring to the
through
the SunGloss system ?
We could provide you with an sdf files containing the final
translations if that helps
Rafaella
(FYI, the NetBeans team is provided with TMX and that greatly
enhances the localization process.)
Jean-Christophe Helary
On 18 juin 07, at 22:22, Alessandro Cattelan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
starting from today I'll have some more free time to dedicate to OOo
L10N so I'd like to start working on it. I'm wondering whether the
Italian team should use OmegaT or poEdit to translate
Hi,
starting from today I'll have some more free time to dedicate to OOo
L10N so I'd like to start working on it. I'm wondering whether the
Italian team should use OmegaT or poEdit to translate the OLH and
possibly the GUI (using Pootle as a translation workflow manager).
Petr, Rafaella, can I
(from the Okapi framework -
LGPL .NET 2.0) to get the proper TMX from this process. Just use
oo2po to get a po file and Rainbow to convert that to TMX.
JC
Please let us know about the outcome.
Rafaella
F Wolff wrote:
On Ma, 2007-06-18 at 22:40 +0900, Jean-Christophe Helary wrote
On 19 juin 07, at 08:26, Arthur Buijs wrote:
Hi,
Rafaella Braconi schreef:
For all the ones who are still looking for the answer to the
question ... yes OmegaT can be definitively be used to translate
the sdf files converted into po files.
Really thank you to Alessandro, Jean-Christophe,
and that greatly
enhances the localization process.)
Jean-Christophe Helary
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 16 juin 07, at 04:48, Alessandro Cattelan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I ran a couple of test to see whether OmegaT could be used to
translate
the OLH for OOo 2.3 and I forgot to post the results here as a
follow-up
to this discussion (I've sent them to Sun
Ale,
If non-pootle users still want to use TMs it is possible to use
OmegaT too.
I should have thought about that a couple of weeks ago, before going
around looking for info on PO editors and all the rest. I think I've
missed the point in which OmegaT started supporting PO files... :o(
format but I leave that to others.
I know some already use it here. NetBeans localizers also use it
intensively. And real translators too :)
Jean-Christophe Helary (OOo-fr)
http://sourceforge.net/projects/omegat/
CVS veersion:
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/
omegat co -P omegat
On 11 juin 07, at 09:11, Alessandro Cattelan wrote:
I'd been told before that it should be quite easy to convert a txt
into
PO but unfortunately I don't know how to do it.
Basically what I have is a long list of terms and expressions in two
tab-separated columns, one for the English version
On 1 juin 07, at 03:14, Alessandro Cattelan wrote:
We've been asked to use the PO format because in a past project
converting to XLZ and back-converting to PO created quite a few
problems. I would be much happier using some other tool such as
Heartsome XLIFF Editor but I'd like to avoid
On 31 mai 07, at 03:39, Alessandro Cattelan wrote:
Hi,
I'll be working on the Italian translation for OOo 2.3. For the GUI
translation we'll be using Pootle whereas for the translation of the
online help we'll be using a PO editor.
Ale,
Is this the file you mentioned on l4t ? If yes, I was
remember seeing any announcement on any list of users of TMX.
The release is made for public comments but I also did not find
anywhere the comments made in the last 3 weeks were made public.
Did I miss a link ?
Jean-Christophe Helary
OmegaT
is wrong.
Or maybe you mean messy by large, in which case, you may be
right. As I pointed out earlier today: plenty of redundant
information all over the place, but to get _the_ tiny bit the one
misses the suggestion is to subscribe to _yet_ another mailing list...
Jean-Christophe Helary
On 19 janv. 07, at 15:45, Jean-Christophe Helary wrote:
why is the translate toolkit necessary ?
Sorry to have brought the thread to a place far from where I expected
it to go...
Anyway, I installed the translate toolkit and read the documentation
and I eventually figured out that we
These pages have unique information, doubled information, uptodate
information, old information and irrelevant information ;)
Someone writing good English should merge this information and
outline as
you described. In Wiki of course.
Ok :)
JC
it in OmegaT etc.
From there I had a discussion with Sophie about the source file
format issue and she advised that I joined the discussion here.
JC
On 19 janv. 07, at 16:46, Ain Vagula wrote:
On 1/19/07, Jean-Christophe Helary [EMAIL PROTECTED] wrote:
Clytie, Ain (?)
I have 2 questions: why
On 19 janv. 07, at 17:25, Clytie Siddall wrote:
I was on the IRC last night (brandelune)
I wish there were tooltips or something so you could tell who
people are.
Well, on mine (xchat/osx) you just click on the person and the
registered name appears.
ps: OmegaT has a PO filter given
Ain,
So the question you seem to have with xliff:
On 19 janv. 07, at 19:48, Ain Vagula wrote:
By the way, I noticed that xliff files are stored in packed format,
xlz? It
means that when using xliff as only intermdiate version, without
po-
step,
you'll not have any overview over
You should send that to OLT's list.
https://open-language-tools.dev.java.net/servlets/
ProjectMailingListList;jsessionid=D680E07AC70B0C4E86FCF49D0E2D96EB
JC Helary
On 19 janv. 07, at 14:35, Ain Vagula wrote:
openSUSE 10.2, trying to start OLT:
- with java 1.4.2:
[EMAIL
Clytie, Ain (?)
I have 2 questions: why is the translate toolkit necessary ? And why
aren't there any references to OLT ? The French community
receives .xlz files and would be unable to follow the howto since it
is exclusively based on po files (which is not a bad thing in the
absolute,
but... It's not high on my to-do list.
Jean-Christophe Helary
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
1 - 100 of 101 matches
Mail list logo
