nt to do, NekoDTD may help.
[1] http://www.apache.org/~andyc/neko/doc/dtd/index.html
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
n return start/
end line and column information but many users have
requested character offset information based on the
beginning of the file. So I'll be working on that
feature and fixing more bugs.
As always, the code is available at the following URL:
http://www.apache.org/~andyc/neko/doc/in
Well, it's been way too long since the last update and, while
there aren't many changes, I figured it was important to let
people know that I'm still working on this stuff! :)
Anyway, the short list of updates include:
* NekoHTML
* implemented scanning of XML declaration
* fixed
g to the mailing lists/
commiting code and then mailing status reports to the mailing
list each month? That would certainly help us stay on top of
who is active vs. inactive.
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
community when you only ever hear two voices...
It does seem rather quiet around here. I'm surprised that
noone else has added their ideas to the discussion. Perhaps
they're scared of me. ;)
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
tools they're looking for -- we'd just be moving
the big grab-bag down one level.
allied to XML parsing, it's all good. The only point I'll have to
stick to is that there isn't some magical Xerces entity that contains
all the components of Xerces-* that are considered "
hat are not
part of the TLP are candidates for being made part of a sub-
project. For example, HTML is a good candidate: it would
include the HTML DOM implementation as well as an HTML parser
built on the Xerces framework.
--
Andy Clark * [EMAIL PROTECTED]
-
eally. Although the term "product" is a little clearer in
that it refers to a shipped entity. Perhaps it would be easier
to start by defining what we want to ship and then work backwards
from there.
--
Andy Clark * [EMAIL PROTECTED]
---
el. A sub-project would simply be a section of
code with a community that looked at some element of XML parsing.
Does that make sense?
Sounds good.
(Is XML parsing too confined?)
I don't think so. That's exactly what the Xerces project is
about. (And APIs generated from parsing XML
e
Xerces framework. But the draft charter was explicit about
defining a sub-project as an XML parser implementation in a
particular language.
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
Berin Lautenbach wrote:
All thoughts welcome! I'd very much like to understand what everyone's
feelings are in relation to making Xerces (and the other sub-projects)
TLPs.
I'm in support of making Xerces a top-level project as long
as my concerns with the draft charter are add
ces-* sub-project. For example,
the Xerces-J parser could have an HTML sub-project that
includes the HTML DOM and an HTML parser built on the
XNI foundation.
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mine, I am announcing the new
release now and will work on fixing the server afterwards.
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
arter.
Anyone in dis/agreement? What are your thoughts?
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-projects.
Then, the Xerces sub-projects would include proper sub-
projects of the parser. For example: the HTML and WML DOM
implementations; perhaps an HTML parser built from Xerces;
a Relax NG validator; etc.
Thoughts?
--
Andy Clar
Turns out there was a serious bug in the new namespaces
feature of the latest release of the HTML parser. So here's
a quick update to fix it:
http://www.apache.org/~andyc/neko/doc/index.html
Sorry for the inconvenience.
--
Andy Clark * [EMAIL PROT
matches the document root element name.
As always, you can find the latest downloads at my Apache
website:
http://www.apache.org/~andyc/neko/doc/index.html
Enjoy!
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [E
osal at :
http://nagoya.apache.org/wiki/apachewiki.cgi?XMLProjectPages/FederationProposal
I'll start off with a +1 from me.
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
erter. The details
are in the change log.
As always, you can pick up the release at the following
link:
http://www.apache.org/~andyc/neko/doc/index.html
Enjoy!
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROT
It's been awhile since the last release of my CyberNeko
Tools for XNI -- I've been working on a Palm program that
I'll be releasing soon. Anyway, I've rolled a bunch of
small changes into this release and it's now available
for download.
Here's the list of changes:
HTML Parser 0.8.1
* fixed b
ndard input
These tools (as well as others) are available for download
from my website at the following URL:
http://www.apache.org/~andyc/neko/doc/index.html
Enjoy!
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e
I've fixed some bugs in the CyberNeko HTML Parser and
a bug in the CyberNeko Pull Parser. New versions are
now available at the following URL:
http://www.apache.org/~andyc/neko/doc/index.html
Enjoy!
--
Andy Clark * [EMAIL PROT
I've just posted an update to the CyberNeko Tools for
XNI. This release fixes a number of bugs in the NekoHTML
parser. It can be found at the following URL:
http://www.apache.org/~andyc/neko/doc/index.html
Enjoy!
--
Andy Clark * [EMAIL PROT
I've released an update for the CyberNeko Tools for
XNI so that the existing tools can be compiled and
used with the newly released Xerces-J 2.3.0. It can
be downloaded from the following URL:
http://www.apache.org/~andyc/neko/doc/index.html
Enjoy!
--
Andy Clark * [EMAIL PROT
This release includes an update to the NekoHTML parser
that fixes several reported bugs. Check it out at the
following URL:
http://www.apache.org/~andyc/neko/doc/index.html
--
Andy Clark * [EMAIL PROTECTED]
-
In case of
ince SAX does not
retain any information about the document, the app
would still need to store that information.
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe
functionality.
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I've just posted a new version of the CyberNeko Tools
for XNI to fix a few bugs in the HTML parser. You can
pick it up at the following URL:
http://www.apache.org/~andyc/neko/doc/index.html
Enjoy!
--
Andy Clark * [EMAIL PROT
Sam Ruby wrote:
Andy Clark wrote:
So I say make every project independent (unless
there is a direct, mandatory dependency -- i.e. a
sub-project) and then allow each project to decide
which taxonomy (or taxonomies) that are appropriate.
Is that something you plan to mandate and enforce? If so
cy -- i.e. a
sub-project) and then allow each project to decide
which taxonomy (or taxonomies) that are appropriate.
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail:
!
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
With the release of Xerces-J 2.2.0, some XNI changes
were introduced which required updates to most of the
NekoXNI tools. I've made the changes so that the tools
can be compiled/run with all versions of Xerces2
starting with 2.0.0 through 2.2.0. (The only one that
can't be built with the new versi
imary difference is the hierarchy of
classes with public fields to access the document info.
Does this work for people? Is it worthwhile to pursue
a native implementation of this approach?
All questions, comments, and concerns are welcome.
--
Andy Clark * [EMAIL PROT
It's been a long time since the last release of the CyberNeko
Tools for XNI. (I hope it's worth the wait. :) I wanted to
release a lot early than this but I've been pretty busy --
you know how that goes... Anyway, I'm now pleased to announce
that the CyberNeko Tools for XNI 2002.08.25 is now avail
sting pull-parsing projects such
as XPP. Rather, it is meant to show the flexibility and
power of the XNI framework to address other parsing needs
while leveraging the existing library of XNI components.
--
Andy Clark * [EMAIL PROTECTED]
-
the
"attr2" attribute is in the "NSa" namespace.
Therefore, what you are seeing is not a bug in any of
the parsers that you are using (unless, of course, that
the parsers *are* returning namespace information for
unprefixed attributes). Namespaces in XM
o/doc/style/
[2] http://www.apache.org/~andyc/neko/nekostyle-0.1.zip
http://www.apache.org/~andyc/neko/nekostyle-0.1.tar.gz
[3] http://www.apache.org/~andyc/neko/nekoxni-2002.06.18.zip
http://www.apache.org/~andyc/neko/
s and adding new
tools as time permits. But I'll announce them here
when they're available.
Enjoy!
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
thought they were already but I found a few problems in the
ordering so I fixed it. (Perhaps I'm studying too much
Japanese... ;)
Enjoy!
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTE
I fixed the horrendous bug in the tag balancer that I
introduced in the last version. Sorry 'bout that! :/
The latest version can be downloaded from the web page:
http://www.apache.org/~andyc/nekohtml/doc/index.html
Enjoy!
--
Andy Clark * [EMAIL PROT
Looks like I botched the tag balancing code when I added the
performance improvements. I'll be looking at fixing this as
soon as possible and posting a new release. Sorry for the
inconvenience.
--
Andy Clark * [EMAIL PROT
arser (DOM,
specifically) but that will have to wait until a future
release. If anyone has additional feature requests, let
me know.
Enjoy!
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTE
framework?
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Parser or SAXParser which have
more dependencies), then you can just use the NekoHTML
Jar file and the minimal Xerces Jar file. This greatly
reduces the size of the required files.
I see a huge savings because I write directly to XNI.
Compare fo
s for HTML/XML tools that I will
continue to develop and release to the community. I'm
writing them for my own personal use but you may also
find them useful.
Enjoy!
--
Andy Clark * [EMAIL PROTECTED]
-
In case of t
ces2. In fact, I should add it anyway
because I know other people would use it as well. For
example, way back when the Xalan folks were talking about
having better control over the char buffers so that they
didn't constantly have to copy chars around.
It's fun to be able to program
output;
* Samples and more documentation to show how to use NekoHTML;
* Lots of cool tools built from NekoHTML and Xerces2;
* ...etc...
But that will have to wait until I have more time... :)
You can download the latest packages from the following URL:
http://www.apache.org/~andyc/
--
Andy
So if everyone still wants it to go forward for inclusion in
the Xerces codebase, let's do it. But let's figure out all of
the sub-project details first (e.g. HTML and WML DOMs; the
serializers; as well as future donations).
--
Andy Clark * [EMAIL PROTECTED]
---
s the current procedure
> to create sub project?
With the current state of the pull API and implementations,
it might be better as it currently is -- hosted elsewhere --
but with a link from the Xerces2 pages listing all of the
projects that are
hat's
not to say it can't work for all XNI pull-parsing configurations
and that there's no value in such an attempt. It might even be
fun to try. :)
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail:
as very little change in terms of behavior
but includes a bunch of useful new features.
Have fun!
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROT
uch slower when the jars are compressed.
True.
> As for the subprojects, I would suggest Xerces to do 'internal
> subprojects' like Avalon or Turbine do on Jakarta. In this case, it will
> make perfect sense to have the HTML parser there.
Okay, I'll look into
cts to
be more aware of XNI and its ability to solve advanced
problems.
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional com
on adding
the infoset augmentations, updating the docs, and pushing a
new version out the door. [Disclaimer: but don't kill me if
it doesn't get out there until tomorrow.]
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ations to indicate "synthesized" events.
After that, it's just a matter of updating the docs and
releasing the new version.
But I'm getting tired so I'll probably do that tomorrow.
--
Andy Clark * [EMAIL PROTECTED]
---
tell if anyone still needs uncompressed Jar
files by the amount of screaming and cursing. :)
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
scussion, NekoHTML
will either be rolled into Xerces OR become a separate project
of its own. In the latter case, it's not clear whether separate
projects are included in the Xerces codebase (but kept separate)
or hosted elsewhere.
I have no problem with NekoHTML remaining separate but it would
be nice to have links to related projects from the Xerces page,
as you suggest.
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
they be in the xml-xerces
module? In their own module? Or should they be hosted elsewhere?
Anybody have thoughts on this topic?
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscri
It sounds like people are divided between including it with
Xerces and leaving it as a separate project. Perhaps this is
the critical mass we needed to fully explore how to handle
separate (but related) projects.
I'll start a separate thread for
kind
of functionality in the parser package itself, I'm putting
it to a vote of the Xerces developers.
[Q] Should we add NekoHTML to the Xerces-J codebase?
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail:
with Xerces. Certainly if there is a need
for it, I wouldn't mind rolling it into the codebase -- it's
actually quite small so it wouldn't add a lot to the source
or Jar file(s).
What do people think?
--
Andy Clark * [EMAIL PROTECTED]
---
arsing an HTML file by using the Xerces HTML
DOM implementation. Please read the documentation for
details.
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail:
's located at the following URL:
http://www.apache.org/~andyc/
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional c
bly SourceForge.
In short, development will continue as warranted. There are a
few things in JTidy that look useful so that may be the next
step I take with NekoHTML.
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-m
the Xerces
codebase so the next release of Xerces will solve these
problems. You can download the latest code from:
http://www.apache.org/~andyc/
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail:
ashdot, etc) and
it handles them pretty well.
So I would like people to try it out and let me know
whether it's worth integrating into Xerces-J.
--
Andy Clark * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL P
nge the decoder
of the stream than to go through all of this trouble,
right? Not unless I want to re-write every known character
decoder. So I'm stuck with this kind of a solution. But
it seems to work very well.
--
Andy Clark * [EMAIL PROTECTED]
-
parse HTML documents
please try out the HTML parser and let me know what you think.
There should be enough information in the documentation to get
you started. Check out the "NekoHTML" project listed on my
Apache web site: http://www.apache.or
build the code. Plus, some of the URLs may require
a user to register and/or accept some license agreement before
downloading the package which would complicate the process of
automating the download.
So, licenses permitting, I would prefer to keep the jar files
in the repository.
--
Andy Cla
Congratulations everyone on the release of Xerces 2.0.0. It was a long
time coming but now it's done. Yay!
BTW, I just posted the announcement to Freshmeat.
-AndyC
<>
-
In case of troubles, e-mail: [EMAIL PROTECTE
EMAIL PROTECTED]
Cc:
Objet: AW: RE: Involve HTML Entities in XML
That's what I thought, but at the moment I don't know how to
change the font of my display, do you or anyone else?
-Ursprüngliche Nachricht-----
Just because you see question marks doesn't necessarilly mean that the
parser is incorrectly handling Unicode. It may just be a font problem --
i.e. your display font doesn't have glyphs for these character points.
-Ac
Message d'origine
De: Kerstin Kohl
Payal,
You need to do your homework more. First, the SAX characters callback is
not guaranteed to return all the characters between elements, etc. in a
single call. You can find this documented in the SAX API. Therefore,
your code *will* fail anytime that the character content that you need
giacomo wrote:
> Another point is (yes, guys, it comes again) shouldn't we move to a
> more "official" DTD for our docs? The Avalon project already has parts
> of their documents written in DocBook as well as XSLT stylesheets to
+1 for DocBook (or a subset)
--
Andy
- Original Message -
From: "Bob Jamison" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, December 02, 2001 3:46 AM
Subject: Re: [xerces2] info about some packaging changes
> A SAX-only jar would be feasable, at any rate. I
> have built a smaller jar that contains mostly SAX s
logo overlaps the title
bar looks odd. It would be better if it completely overlapped
that bar with an equal size on both sides, if you know what
I mean.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
-
In case of troubles, e
[EMAIL PROTECTED] wrote:
> http://www.corrosive.co.uk/xml_apache_org/presentation/
Super cool! I like v3.1.
Just as a side note, I think that fixed-width pages are EVIL.
So any design we come up with should not use them.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTEC
[EMAIL PROTECTED] wrote:
> How about framesets to avoid "complex tables"?
I know some people don't like framesets but it would make the
content easier to print -- having a navbar in printed material
doesn't make sense, anyway.
--
Andy Clark * IBM, TRL - J
at can, do.
Those that can't, complain. :)
Now, seriously...
I'd like to propose that we come up with some style guide
so that all of the XML sub-projects look like they're
related but not *exactly* the same. It would be great if
each project developed its own stylistic persona.
Robert Stuart wrote:
> Xilo - pronounced as Silo, as in repository?
That's good! I like Xilo. :)
> I must admit, I quite like "Xintian", but feel we should aim for gender
> neutral names.
How do we know that "Xintian" isn't the Chinese equivalent
of "
Kimbro Staken wrote:
> I'd like to propose that the name Xindice be adopted for the new XML
> database project.
Since it's a database, how about calling it "XLOB"? (That's
pronounced as "slob".) :)
--
Andy Cl
efined in HTML which is a grammar
defined using SGML. XML only defines five built-in entities
by default: "lt", "gt", "amp", "quot", and "apos". If you
want to use other entities, then you must declare them in
the DTD, either using the internal s
I fixed the links on the main page to point to SourceForge. The
changes will be in the next release.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e
to have a
network connection.
So I say that we keep Xerces-J the way it is now.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EM
encies in their own code base,
or work out a system that pulls a tagged version of the
common code from CVS, I say that's fine but the decision
should be left to the project developers.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
---
ly pulling the
latest copies of things from xml-commons in the build is the
right thing to do. Yes, projects should take every effort to
stay up to date with the commons packages but it should not be
a required part of the build process.
--
Andy Clark * IBM, TRL - Japan * [E
community long enough to know so my
worries may be ill-founded. In any case, I'm in favor of having
a community based implementation of UDDI at Apache.
What do other people think?
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
-
is for external parsed entities. (Both look
like , though.)
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
, and easier to
maintain. Applications using only the standard interfaces such
as JAXP, DOM, and SAX should not see any differences.
To get involved with Xerces2 development: download the beta
release, subscribe to the xerces-j-dev mailing list, and start
writing really great code!
--
Andy C
otocol but
the classes handle it automatically when you use them.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ypes? All of which is pretty essential
to our documentation.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For a
it!) or Cocoon2 (which is supposed
to be the biggest baddest dude on the block), I don't care.
However, I *would* like the tools required to build the
docs be as small as possible, though.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
---
th Xerces2.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Sounds good to me. +1
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Vivek Chopra wrote:
> Is this workshop open to all? What do I need to
> do sign up? Sorry.. I wandered into this mailing
> list kind of late!
Yes, it is open to all but I am requiring people to register.
So consider yourself registered! :) See you there.
--
Andy Clark * IBM, TR
diagonally) from the Donut Wheel.
A sample map is attached to this message.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
97 matches
Mail list logo
