From: Steffen Wolfrum <wlfrm@estfiles.de>
Subject: Re: Support ... (was: Support bei Einstieg in ConText)
Date: Sat, 27 Sep 2003 12:47:51 +0200 [thread overview]
Message-ID: <a05210612bb9b1b53173d@[217.184.8.69]> (raw)
>The following message was sent by Patrick Gundlach <pg@levana.de> on Sat, 27 Sep 2003 07:32:02 +0200.
>
>> Steffen Wolfrum <wlfrm@estfiles.de> writes:
>>
>> Hi,
>>
>> > Gibt es etwa B¸cher zum Thema ConTeXt?
>>
>> come on, guys. Posting in a wrong language can happen. So what.
>> Answering (an obviously private mail posted in the ML) here in the
>> same language on this mailinglist is not the best thing, but this can happen,
>> too. But we should not keep up this german thread. It is not polite
>> for the other non-german speaking people out there, that get
>> completely bored. So I'd suggest:
>>
>> \if\language\en\postonthismailinglist=1
>> \else
>> \dontexpand & \keepitprivate
>> \bye
>> \fi
>>
>> Patrick
>> --
>> You are your own rainbow!
Hi Patrick,
Somehow I really felt like walking on thin ice when I wrote the email you mention.
Well, I knew it will be difficult to serve the different aims of communication:
- politeness and
- political correctness
I asked some friends, and we discussed on this topic, trying to find a suitable way,
to get the message transferred, and not to hurt anybodies feelings - as the later is very quickly done, and it's a pity, cause often quite unnecessary.
So finally, after carefully looking at the pro and cons, I decided to write a bi-lingual answer, exactly one sentence each:
> Gibt es etwa Bücher zum Thema ConTeXt?
> (Did you ment editing books *on* ConTeXt?)
Sure, I have to admit that I used brackets for the second sentence.
Btw.: Why didn't you quote that second sentence?
So it might have given you the feeling that I made a *main* answer and a less important.
But my intention was only to stay in the logical structure of the mail I was answering to:
- Jörg once started a threat in German - ok, as you told him this was an initial mistake.
- Willi (a typical multilingual Dutch) also answered in German
So I wrote my contribution also in the main language of this thread,
AND, to stay in the rules of the mailing list, I translated it, as best as I could, into a kind of international English.
Obviously my mistake were the brackets.
I knew I am walking on thin ice ... and so I forgot to look on my orthography carefully.
Thank you Patrick for pointing me to that.
Steffen
P.S. Who got bored?
next prev reply other threads:[~2003-09-27 10:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 8:47 Support bei Einstieg in ConText ml-context
2003-09-26 18:45 ` Willi Egger
2003-09-26 21:04 ` Steffen Wolfrum
2003-09-27 5:32 ` Patrick Gundlach
2003-09-27 9:43 ` Willi Egger
2003-09-27 10:01 ` Hans Hagen
2003-09-27 11:28 ` Patrick Gundlach
2003-09-27 10:47 ` Steffen Wolfrum [this message]
2003-09-27 12:12 ` Support Patrick Gundlach
2003-09-27 12:56 ` Re: Support bei Einstieg in ConText Matthew Huggett
[not found] <200309270929.h8R9TcK23548@twilight.domainfactory.de>
2003-09-27 10:29 ` Support ... (was: Support bei Einstieg in ConText) Steffen Wolfrum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='a05210612bb9b1b53173d@[217.184.8.69]' \
--to=wlfrm@estfiles.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).