From: Stefan M. <sm...@oe...> - 2008-11-03 19:23:22
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list! There was some off-list discussion between DaveK, Matt and me. Matt seems to be unable to process private mail properly and asked us to move to the list. Since at least I am not following this list very closely (because I have only time for "my" sub-projects) we want to put a special token in the subject line so the respective threads are easy to recognize. I suggest we use "{ODF}". The braces don't interfere with the mailing list tag and "ODF" is short enough to be recognized. Also I don't know whether there is a policy on this list regulating such things - for instance to limit traffic. DavidG? Hi Matt and DaveK! @Matt: It would be very useful if you could tell us what exactly from S5 you are trying to mimic. 4 days ago Dave Kuhlman wrote: > m h <sesquile <at> gmail.com> writes: >> Isn't there a >> combinatoric explosion with say a big, right aligned bold monospaced, >> etc font? How do you handle that? > > Until you asked, I was able to ignore it. Does this mean that I can > no longer do so? Does it seem to be a problem? What Matt names above are three inline layouts (big, bold, monospaced) and one block layout (right aligned). AFAICS in reST there is simply no way to combine inline layouts so there is no possibility for combinatoric explosion. In fact reST does it right to markup the meaning - such as emphasis - instead of a certain layout. How you translate meaning to layout depends much on the channel you are using. For instance in an audio format you would probably say something with emphasis louder. If you use classes - which are block level - you may annotate a block with several classes. If these classes are translated into layout information then you have to deal with combinations there. Grüße Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/> iQCVAwUBSQ7M6AnTZgC3zSk5AQLcsAP/dHkZywqWJ+ABhOMP+y+/VfrvIoggsIMN ndc6d7lS2clTG8ieaCI3F+sdNtmkBKVTY5WE3K7lgTWnCY1umun3n34KPEe5A648 +CVvuSi8/iwdaAGLPWBHSuCUhp1S3iMSVA+Xdt9n2d1wjJk4eBl3FXGxtF9yZwkk +Mgm/1D+Alo= =dbGz -----END PGP SIGNATURE----- |