Return-Path: Received: from topo.math.u-psud.fr ([129.175.50.180] verified) by vsu.ru (CommuniGate Pro SMTP 3.3) with ESMTP id 1772826 for CyrTeX-en@vsu.ru; Tue, 01 Aug 2000 14:39:22 +0400 Received: from lcs by topo.math.u-psud.fr with local (Exim 2.10 #1) id 13JZQY-0006Zm-00; Tue, 1 Aug 2000 12:37:38 +0200 To: CyrTeX-en@vsu.ru, lcs@topo.math.u-psud.fr Subject: Re: input encoding question Message-Id: From: Laurent Siebenmann Date: Tue, 1 Aug 2000 12:37:38 +0200 Dear Anatoliy, I wrote that LS> The common-names and hexadecimal codes > in Windows 1251 encoding are: > > double left guillemets (<<) "AB > double right guillemets (>>) "BB > single left guillemet (<) "8B > single right guillemet (>) "9B You correctly answered that the latex tags are guillemotleft guillemotright guilsinglleft guilsinglright These come from Adobe and the the first two involve novel :=/ Adobe misspellings (mot <== met). However contrary to what you say, guillemotleft and guillemotright are not entirely absent from the variants of code page (cp) 866. In my copy of cyinpenc.dtx they are present in the New Alternative Variant cp866nav at positions "FD and "FE. guillemotleft "FD guillemotright "FE Since you mention that cp866nav is state standard in the Ukraine guillemotleft guillemotright definitely deserve support. By the bye, the Russian number symbol \CYRNo is present in all variants of cp 866 (except cp866mav = "Modified Altarnative Variant") and the location is "FC so it deserves support too. *Everything* I know about cp866 is 100% hearsay. Mistakes and omissions are like flies on ripe fruit. I wish I had ".gif" tables for cp 866 and variants; they make the flies more obvious! More comments? Cheers, Laurent S PS. Any tentative answers to my other questions?