Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


On Tue, Nov 23, 2010 at 2:20 PM, Larry Gusaas <larry.gusaas@gmail.com>wrote:

On 2010/11/23 12:25 PM  Kevin Vermeer wrote:

This only happens on this list, because every subject is prepended with
[tdf-discuss] and some replies get  Re: inserted after it while others
insert the Re: before the [tdf-discuss] token, leading to four kinds of
subjects like:


Once again I am glad that I follow this list as a newsgroup through gmane.
None of the post I get have [tdf-discuss] in the subject line.

As for the insertion of the Re:, that is determined by the email client.
Some insert it before, some after [tdf-discuss].


Why does gmane remove it?  It's clearly a part of the subject, if you look
at the original headers.   Is filtering with tokens in square brackets a
standardized or recommended practice?  If so, I'll submit a bug report to
the gmail team, and that will be the end of it.

However, gmane is the only client I'm aware of that handles it in a special
way (based on the gmail web interface and Mozilla Thunderbird and Apple Mail
tools).  If the action it takes is to strip it, then why bother in the first
place?
--
Kevin Vermeer

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.