Return-Path: Received: from video.uic.vsu.ru ([62.76.169.38] verified) by vsu.ru (CommuniGate Pro SMTP 3.2b7) with ESMTP id 1163827 for CyrTeX-en@vsu.ru; Thu, 16 Dec 1999 13:26:15 +0300 Sender: vvv@video.uic.vsu.ru To: (Cyrillic TeX Users Group) Subject: Re: *complete* WLCY References: From: Vladimir Volovich Date: 16 Dec 1999 13:26:43 +0300 In-Reply-To: Laurent Siebenmann's message of "Thu, 16 Dec 1999 04:38:42 +0100" Message-ID: Lines: 43 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Dear Laurent, "LS" == Laurent Siebenmann writes: LS> Incidentally, the AMS openly invites others to complete and LS> support the WLCY variant of the AMs WNCY fonts. It would be LS> ideal if your group would do this since this list is well placed LS> to debug and criticize them, if that proves necessary. The full LS> WLCY is a smaller job than the one you have just done for the WN LS> fonts! moreover, making fonts with the help of a small script makes the job of creating missing WLCY fonts very simple. :) so it could be done. i have one question. WLCY fonts remove all ligatures but the following: ' ' => '' (quoteright quoteright -> quotedblright) - - => endash endash - => emdash In WNCY fonts, there exists also the following non-letter ligatures: [ [ => guillemotleft ] ] => guillemotright (guillemets in WNCY fonts are also accessible via characters < and > without ligatures; in other cyrillic font encodings, guillemets are accessible via ligatures << and >>). The question is: what one should do with guillemets in WLCY (and WL) fonts: * do not provide ligatures (as currently in WLCY), so the guillemets are accessible only via characters < and > (and commands \guillemotleft, \guillemotright) * do not remove ligatures [[ and ]] * remove ligatures [[ and ]], but add ligatures << and >> (so guillemets will be accessible both as < > and << >>). Best, v.