Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news1.tnib.de!feed.news.tnib.de!news.tnib.de!news.belwue.de!rz.uni-karlsruhe.de!feed.news.schlund.de!schlund.de!news.online.de!not-for-mail From: "Joachim Schmitz" Newsgroups: comp.lang.c Subject: Re: trigraphs, yecch Date: Wed, 1 Feb 2012 10:39:05 +0100 Organization: 1&1 Internet AG Lines: 13 Message-ID: References: <4f2808f4.648026530@text.giganews.com> <86aa53e59d.fsf@zipcon.net> Reply-To: "Joachim Schmitz" NNTP-Posting-Host: dsdf-4db5ec31.pool.mediaways.net Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 8bit X-Trace: online.de 1328089152 2189 77.181.236.49 (1 Feb 2012 09:39:12 GMT) X-Complaints-To: abuse@einsundeins.com NNTP-Posting-Date: Wed, 1 Feb 2012 09:39:12 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Xref: x330-a1.tempe.blueboxinc.net comp.lang.c:16579 James Kuyper wrote: > There are work-arounds; such as standard conventions for > transliterating a German letter such as ö into oe, but those > conventions implement essentially the same idea as trigraphs: using > multiple representable characters to indirectly represent a single > character that's not directly representable. Not quite the same thing. while e.g. the German ö can get transcribed as oe, not every oe can get changed to ö, so the process is not reversible. Bye, Jojo