Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: highlighting and fontification
Date: 10 Sep 1999 21:01:56 +0200	[thread overview]
Message-ID: <vafso4mk2u3.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Stainless Steel Rat's message of "10 Sep 1999 14:29:08 -0400"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> Okay, I suppose that I should have said that it is an American
> typographical convention.  There are a lot of little differences
> between American and European typography.  This is one of them.

Ah.  So, to borrow some HTML:

Americans emphasize like <em>this?</em>
And Europeans emphasise like <em>this</em>?

Very interesting.  I care about these little differences.  But since
I'm not a native English speaker, things start to get vague for me.
For instance, should I assume that I'm writing British English if my
text contains a lot of `old chap' and `lift' and adjust my typography
accordingly, as opposed to `hey, guys' and `elevator'?

The situation is worse for Germans writing about computers (in
German): the German word for `to backup' is `sichern', which is a
homonym (or polyseme?) and also means `to make secure'.  Thus, the
word `Backup' is likely to be used as a noun in a German text, but it
is not clear at all how to make that into a verb.  In speech, one will
say `wurde gebackupt' (for `has been backed up'), but the spelling is
not at all clear: maybe `wurde gebackupped' with a pseudo-English
suffix which is pronounced the same as the other one?  But in German,
the prepositions are separated from the noun, maybe `wurde upgebackt'
would be better?  Even though Germans would laugh when seeing that,
they don't think twice about saying `Ich bin eingeloggt' (I am
logged in).

I think the French approach the whole thing by not using English words
(at least officially) -- ordinateur instead of computer and so on...

How do other nations deal with this?

8-)

Sorry for the off-topic posting, hope it is interesting anyway.

kai
-- 
I like BOTH kinds of music.


  reply	other threads:[~1999-09-10 19:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-09 17:51 Daniel Monjar
1999-09-09 21:55 ` Jack Vinson
1999-09-09 22:34 ` Karl Kleinpaste
1999-09-10 15:35   ` Stainless Steel Rat
1999-09-10 16:24     ` Kai Großjohann
1999-09-10 16:32       ` Emerick Rogul
1999-09-10 18:29       ` Stainless Steel Rat
1999-09-10 19:01         ` Kai Großjohann [this message]
1999-09-12  5:16           ` Stainless Steel Rat
1999-09-13  9:17             ` Michael Piotrowski
1999-09-13 18:32             ` Florian Weimer
1999-09-13 21:46               ` Mick Gower
1999-09-15 22:13                 ` Edward J. Sabol
1999-09-19  2:56                   ` Greg Stark
1999-09-25  0:47                   ` Ken McGlothlen
1999-10-05  1:40                   ` François Pinard
1999-10-05 14:13                     ` Hrvoje Niksic
1999-10-05 22:49                       ` Russ Allbery
1999-10-06  0:45                         ` David Coe
1999-09-14 12:33               ` Toby Speight
1999-09-14  8:24             ` Tibor Simko
1999-09-11  1:44         ` Rene H. Larsen
1999-09-11  7:06           ` Graham Murray
1999-09-12  5:05             ` Stainless Steel Rat

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=vafso4mk2u3.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).