X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Sat, 10 Mar 2012 00:52:15 +0100 From: Kai-Martin Subject: Re: [geda-user] Text formatting To: geda-user AT delorie DOT com In-Reply-To: <1331314039.2533.16.camel@AMD64X2.fritz.box> (from mail AT ssalewski DOT de on Fri Mar 9 18:27:19 2012) X-Mailer: Balsa 2.4.10 Message-Id: <1331337138.10630.1@kwak> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=PGP-SHA1; boundary="=-qUWQUZ0mtBfHlb8cOnuW" X-Spam_score: -2.9 X-Spam_bar: -- X-Provags-ID: V02:K0:nMXIETC65iIyMBylYzDXpsK5HiZ4q+4dN8kcB+YWn+0 l8xneiCmqkwpJyGuqcNdbKH9ZdbmgpwCEAP86Fp1TmuZmDBa9A 23+fwREcOhAkZDd+XeF3XRPAi9ucrv9DhOYA9dAvX2ZGek61bf TQrGpvGU+Eoj3LnfAdng+sMpidc6vXp7zl72yx9U2DzGuo9Re5 peMaS1DMDo1xqJXiMmFOPwuVzmUE2nrL8wP2B1YTIBkmE8/mb2 kGB2DE3FhqP+gUCw0uiPOsvF0g39H0BOLKAV3obREzM61Cv0do +8ERBo+wesBMoLscLIbzIUz4p4+c5FWJhHhFCHK4+c/XxjG/A= = Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --=-qUWQUZ0mtBfHlb8cOnuW Content-Type: text/plain; charset=ISO-8859-1; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 03/09/2012 06:27:19 PM, Stefan Salewski wrote: > What may we need beside subscript? Too much layout options may look > cluttered in schematics. This is a matter of style and taste. Like with all design decisions, a perfect tool would not enforce a certain style but put the user in control. > Do we desire >=20 > -bold > -italics > -underline > -superscript > -various font faces Whatever a user deems appropriate :-) > How can we add this, without breaking existing code? My favorite: Add the ability to parse and render latex commands. This would end the demand for more advanced text format features once and for all. As an additional benefit, it would allow for equations and the complete set of math symbols. It might integrate with minimum interference with current code and designs: 1) LaTeX interpretation is only performed, if a global attribute latex exists and contains the value "yes". 2) A global attribute latex-pre can contain a header that adds to strings before they are fed to the latex interpreter. 3) On screen, the render engine recognizes some common and simple latex commands. These commands are rendered in a simplified, yet intuitive way. E.g. bold,italics, subscript, superscript, ... 4) On print, all strings are processed by the latex interpreter to render as EPS-snippets. For postscript output, these snippets get pasted to the document instead of the original string. For PNG output, the snippets get converted to PNG with any of the native ghostscript tools. Yes, this would only work, if latex is installed locally. But it would not burden geda developers with the subtleties of text formatting. ---<)kaimartin(>--- --=20 Kai-Martin Knaak Email: kmk AT familieknaak DOT de =D6ffentlicher PGP-Schl=FCssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=3D0x6C0B9F53= --=-qUWQUZ0mtBfHlb8cOnuW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEABECAAYFAk9al7IACgkQt9RkiGwLn1PlMQCgt1DWZQ87kBNGf4BhbI6kr2Ou SAsAniDaNP6JdLHEVZ+NMtz+4HEtHH2a =za1u -----END PGP SIGNATURE----- --=-qUWQUZ0mtBfHlb8cOnuW--