Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Thread

Re: [Digital BW] Spelling Hahnemuehle,was: Subject and Header Lines

Re: [Digital BW] Spelling Hahnemuehle,was: Subject and Header Lines

2001-08-06 by Jerry Olson

How do you pronounce hahanemule?

ruhrfoto@... wrote:
Show quoted textHide quoted text
> --- In DigitalBlackandWhiteThePrint@y..., mwesley250@e... wrote:
>
> > PLEASE DO NOT USE SPECIAL CHARACTERS IN SUBJECT LINES.
>
> > Unfortunately special characters also include many standard
> > European characters that are not included in the American alphabet
> > Re: Hahnem\ufffdhle in Los Angeles, CA:Freestyle
> > Which when displayed on the group homepage (not on e-mailed posts
> > fortunately) are rendered by Yahoo
> > RE:_=5BDigital_BW=5D_Re:_Hahnem=FC
> > Basically the "\ufffd" causes Yahoo to lose it's mind and to start
> > substituting garbage. > Martin
>
> Martin,
> it is a crux with the German "Umlaute" \ufffd, \ufffd, \ufffd.
> Unfortunately the \ufffd occurs in the Hahnem\ufffdhle brand, so many Headers
> in this and other lists are corrupted.
> In Germany we would avoid the problem by changing the
>
> \ufffd to ae
> \ufffd to oe
> \ufffd to ue
>
> But the American list members seem to prefer to skip the e.
> So there are two possible variations to avoid the "Umlaut"-problem in
> spelling Hahnem\ufffdhle (ore others) in headers:
> 1. Hahnemuhle (American)
> 2. Hahnemuehle (German).
>
> To keep the archives searchable, which one shall we use???
>
> Bernd
>
>
> If you do not wish to belong to Digital B&W, The Print, you may
> unsubscribe by sending an email to:
> DigitalBlackandWhiteThePrint-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Re: Spelling Hahnemuehle (4 Jerry only)

2001-08-06 by ruhrfoto@yahoo.de

Jerry,

happy to hear you laughing about my trivial message ... here is 
some more rediculous stuff:
I was a subscriber to VIewCamera for several years.
In their classified ads (Lens and Repro has a double sided one) 
Schneider lenses frequently  show up as Schnieder - while 
Voigtländer lenses always appear as Voightlander (where is that 
"h" from??) .
You see, it is not that easy with a foreign language, istn´t it ?

BTW: same thing with Koka Kohla over here in Germany.

Bernd










--- In DigitalBlackandWhiteThePrint@y..., Jerry Olson 
<jerryolson@r...> wrote:
> How do you pronounce hahanemule?
> 
> ruhrfoto@y... wrote:
> 
> > --- In DigitalBlackandWhiteThePrint@y..., mwesley250@e... 
wrote:
> >
> > > PLEASE DO NOT USE SPECIAL CHARACTERS IN 
SUBJECT LINES.
> >
> > > Unfortunately special characters also include many 
standard
> > > European characters that are not included in the American 
alphabet
> > > Re: Hahnemühle in Los Angeles, CA:Freestyle
> > > Which when displayed on the group homepage (not on 
e-mailed posts
> > > fortunately) are rendered by Yahoo
> > > RE:_=5BDigital_BW=5D_Re:_Hahnem=FC
> > > Basically the "ü" causes Yahoo to lose it's mind and to start
> > > substituting garbage. > Martin
> >
> > Martin,
> > it is a crux with the German "Umlaute" ä, ö, ü.
> > Unfortunately the ü occurs in the Hahnemühle brand, so 
many Headers
> > in this and other lists are corrupted.
> > In Germany we would avoid the problem by changing the
> >
> > ä to ae
> > ö to oe
> > ü to ue
> >
> > But the American list members seem to prefer to skip the e.
> > So there are two possible variations to avoid the 
"Umlaut"-problem in
> > spelling Hahnemühle (ore others) in headers:
> > 1. Hahnemuhle (American)
> > 2. Hahnemuehle (German).
> >
> > To keep the archives searchable, which one shall we 
use???
> >
> > Bernd
> >
> >
> > If you do not wish to belong to Digital B&W, The Print, you 
may
> > unsubscribe by sending an email to:
> > DigitalBlackandWhiteThePrint-unsubscribe@y...
> >
> >
> >
> > Your use of Yahoo! Groups is subject to 
http://docs.yahoo.com/info/terms/

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.