logo Welcome, Guest. Please Login or Register.
2021-04-10 07:17:11 CoV Wiki
Learn more about the Church of Virus
Home Help Search Login Register
News: Check out the IRC chat feature.

  Church of Virus BBS
  General
  FAQ

  FAQ: Hermitish mail mark-up and citation V2.1
« previous next »
Pages: [1] Reply Notify of replies Send the topic Print 
   Author  Topic: FAQ: Hermitish mail mark-up and citation V2.1  (Read 6001 times)
Hermit
Archon
*****

Posts: 4263
Reputation: 8.35
Rate Hermit



Prime example of a practically perfect person

View Profile WWW
FAQ: Hermitish mail mark-up and citation V2.1
« on: 2002-03-05 13:31:57 »
Reply with quote

FAQ: Hermitish Mark-up v. 2.1

URL: http://virus.lucifer.com/bbs/index.php?board=31;action=display;threadid=11526

[b]Authors:
Hermit

Revision: 2.1B (Full BBS mark-up)

Author’s notes for revision: 2.1B
It has come to my attention that I gave some bad advice in the first proposal for this FAQ in the making. The formatting I suggested, conflicts with the embedding of virus messages in some web mail systems. So without further ado, here is revision II of the FAQ in the making, which also extends and enhances the format based on the suggestions and contributions of others, allows the material to be posted directly and safely to embedded pages, and permits the easy translation to HTML in environments which support this.
In addition, the message numbering system has now been simplified, to allow easier tracking of complex threads, and a message index added to the head of a thread for the same reason.
If you received this FAQ via ASCII email, please ignore the values in square brackets (“[ ]”) until they are explained in the text under Mark-up below.
In case any one wondered, comments, criticisms and suggestions are requested and welcomed.
It should be noted that the “B” suffixed version of this FAQ (i.e. formatted for BBS display) is authoritative, and that the “A” suffixed version is derived from the “B” suffixed version for the purposes of ASCII email.

Status
The use of this system is recommended but not mandated for postings on the CoV. Using it will make it more likely that others will read your submissions and will help to prevent the CoV from becoming a "write only zone." The use of HTML in posting to the CoV is deprecated and should be avoided under any circumstances.

Abbreviated Copyright Notice
Copyright (C) The Church of Virus, 2002. All rights reserved. Unlimited distribution permitted in accordance with the terms of the Full copyright notice below.

Abstract
This FAQ addresses the issues of mail-markup (formatting), citation, titling and snipping.
A preferred approach to dialog mark-up, permitting easy use with ASCII email, as well as providing “safe” markup for display within systems displaying mail-list comments for access by web-browsers is introduced. In addition, the recommended format permits readers and author’s to follow “threaded-discussions” without difficulty.

Table of Contents
    Title
    Authors
    Revision
    Author’s notes for revision
    Status
    Abbreviated Copyright Notice
    Abstract
    Table of Contents
    Introduction
    Preferred Implementation
      Responsibilities
      Elision (or "snipping")
      Subject Line
      Message Index
      Attribution
      Sequence
      Reference
      Later "back quoting"
      Citation
      Dating
      Other Mark-up

        Horizontal line
        Italic text
        Underlined text
        Strikethrough text
        Color text
        Quote text
        Indented list
        Quote code

      Capitalization Hint
      Line Wrapping

    Full copyright notice
    Acknowledgements
    Bibliography
    References
    Authors’ addresses


Introduction
This FAQ is intended to improve the formatting, and referencing of work produced by the members of the Church of Virus, in order to simplify the task of making such works more accessible to the public and other members. In addition, it introduces and documents “Hermitish” threading, a new form of ASCII email threading to allow the easy use of this mark-up system via simple ASCII mail.
Hermitic threading is a simplified mail-markup system designed to allow those other than the authors to more easily follow discussions held in ASCII mail forums, and to ensure the readability of messages by preventing the following kind of thing – especially when it runs to 500 lines:

    Actual example from the CoV mail list:
    > > > > > > > >I TOLD you that this mystical buddhist memebot would advance
    > > > > > > > >from a denial of the self to a denial of the world!
    > > > > > > >
    > > > > > > > Please explain how that statement constitutes a denial
    > > of the world.
    > > > > > > >
    > > > > > > Our "subjective" reality is never purely subjective, for it
    > > > > contains (as
    > > > > > > content) information, stimuli, information, perceptions,
    > > etc. from the
    > > > > > > surrounding world.  To deny such lived experience its
    > > reality is to
    > > > > > > deny the reality of the environong world from which its
    > > content flows.


Preferred Implementation


    Responsibilities

      An initial post in a sequence need not be fully marked up (although it may be in order to appear more attractive and in order to relieve respondents of part of the task). The respondent to any post has the responsibility of marking up the original message and their response.
      Subsequent replies and comments on a message already so marked up, have the responsibility of marking up their reply appropriately and adding their post to the message index.
      Each person sending a message has the responsibility of removing superfluous line breaks caused by wrapping in lame mail clients and possibly removing “>” indentation from their messages.


    Elision (or "snipping")

      When material is omitted from a follow-up post, the omitted material should be denoted by:
      Example:

        <snip>

      It is worth remembering that not everyone has a fast connection, most people have insufficient reading speed, and few want to read a long post for the second time to see where the replies are located.  So use your judgment to keep the volume tolerable. This is important for everyone to remember... snipping is at least as important as list content... because lots of people equate tenacious truncation with netiquette, and they simply won't read posts on a list that is uniformly rude.

      When <snipping> is desirable

        <snipping> is appropriate when you do not disagree on a point, or
        where you state that a point is not worth arguing. It is also worthwhile when
        replying with a short (or even a long) comment to the gist of a previous post, but where you are discussing the totality not the independent points of the post.

      When <snipping> is not desirable

        Don't <snip> something that you take issue with, or some lamer will attack you for removing their arguments and assert that you did this invalidly because you couldn't argue your case effectively rather than just putting back the excised material.
        <Snipping> is not appropriate when your opponent has made a valid point and you do not acknowledge it.

      This last is also a strong hint to avoid being seen as a lamer. If somebody snips something of yours and you choose to reply, simply put it back in place, and observe on why you think your text should not have been <snipped>. If you feel very strongly about this, you might choose to denote the restored material with <snip restored by NAME>.


    Subject Lines

      To maintain the accessibility and readability of the archives, it is important that you reply on subject. If you change the subject in a post, denote this by changing the subject line to something more appropriate.
      When posting a reply to a specific person, it is suggested that you append "Ping name" at the end of the subject line. When replying to such a message you should revert to the original subject or alter the name appropriately.


    Message Index

      To indicate who has replied on a particular thread, and in what order, it is suggested that a “Message Index” be used. This is a simple list at the top of a message, showing who spoke and in what order.
      Example:

        [Hermit 0]
        [Joe Dees 1]
        [Hermit 2]
        [Joe Dees 3]
        [Richard Rich 4]
        [Joe Dees 5]
        [Hermit 6]

      The message number is incremented each time a new respondent replies.


    Attribution

      Each paragraph is identified by the name of the speaker.
      Example:

        [Hermit] Says something.


    Sequence

      When a sequence of communications occur, this is indicated by a suffixed number.
      Example:

        [Hermit 0] A implies B.
        [Somebody 1] So is B True?
        [Hermit 2] Only if A is True.


    Reference

      In order to refer to a particular statement a decimal may be suffixed to the number.
      Example:

        [Hermit 1] Yada, Yada, Yada...
        [Hermit 2.5]  I refer to "some useful reference" which says X.
        [Hermit 2] Yada, Yada, Yada...
        [Somebody 3] I don't think that "some useful reference" is really useful.
        [Hermit 4] But in [Hermit 2.5] I have already provided a reference you can check for yourself.
        [Somebody 5] Yada, Yada, Yada

      It is not necessary to number each paragraph, simply add reference numbers when and where needed – to your own, or anyone else’s posts. When reference numbers are added to a post, they should be done so in sequence. It is always possible to insert a new reference when required by adding another level of decimal.
      Example:

        [Hermit 1.1] existing
        [Hermit 1.15] <--- inserted reference.
        [Hermit 1.2] existing


    Later "back quoting"

      When you need to quote from a previous letter, you may use negative numbers to indicate it precedes the current series.
      Example:

        [Hermit 0] It is clear that...
        [Somebody 1] I don't see that it is clear at all...
        [Hermit 2] Well if we look at [some cross reference] you will see that you said:
        [Somebody -1] From a previous post, possibly on a different thread: Yada, Yada, Yada...
        [Hermit 3] From this is follows...


    Mail Citation

      To refer to a previous post, cite it as:
      Cite a post:

        ["Subject Line", Author, Sent Time]

      If you have a web link to an archive, cite it as follows:
      Cite a post with a text description:

        [ur1=http://site.com/pointer to archive item]"Subject Line", Author, Sent Time[/ur1]

      This allows a post to be found in a large number of ways and prevents the confusion of which post in a sequence sharing a subject line and with multiple participants is actually meant.
      Example:
      or just Cite a post by URL if the post is identified elsewhere in the message:

        [ur1]http://forum.javien.com/XMLmessage.php?id=id::XERAICIg-AhZq-AGI4-DSAO-LyUrYEBwG1Zu[/ur1]

      Example:


    Web URL Citation

      When you cite a web page, affix a date so that others may see when it was last accessed.
      Cite a URL with a text description:

        [ur1=http://virus.lucifer.com]some hyperlinked text accessed 2002-02-01[/ur1]

      Example:
      Or, citing a URL without a text description:

        [ur1]http://virus.lucifer.com[/ur1] accessed 2002-02-01

      Example:
      To include a reference to an image:

        [ img]http://virus.lucifer.com/images/cov.gif[/ img]

      Example:


      To include a reference to a flash image:

        [f1ash=200,200]URL[/f1ash]

      Example:




      Dating

        We recommend the use of the ISO 601 date format which has the following structure: YYYY-MM-DD HH:MM[:SS] [TIMEZONE]. (Refer Status for Date and Time Formats). This automatically sorts things so dated into an appropriate time sequence and allows easy date lookups. Seconds and the time zone may be omitted if unimportant. It is in any case recommended that Universal (i.e. Zulu) time always be used to avoid confusion.


      Other Mark-up

        It is recommended that XML/HTML style bracketing be avoided, to prevent confusing existing embedding of messages from the CoV into web pages, but that square brackets, i.e. "[" and "]" be used instead.

        The following are appropriate codes:
        Draw a horizontal line:

          Code:
          [hr]

          e.g.

        Use Bold Text:

          Code:
          [b]Bold[/b]

          e.g. Bold


        Use Italic Text:

          Code:
          [i]Italic[/i]

          e.g. Italic


        Use Underline Text:

          Code:
          [u]Underlined[/u]

          e.g. Underlined


        Use Strikethrough Text:

          Code:
          [s]strikethrough[/s]

          e.g. strikethrough


        Use Color text (e.g. Red):

          Code:
          [color=Red]Red text[/color]

          e.g. Red text


        Quote text:

          Code:
          [quote]Quoted text[/quote]

          e.g.
          Quote:
          Quoted text


        Form an indented list:

          Code:

          [list]some list
          more list
          last list[/list]

          e.g.
            some list
            more list
            last list


        [b]Cite “Code”, i.e. show the value of tags rather than performing the function of the code.[b]

          Code:
          [ code]Some text [b]containing[/b] code[/ code]

          e.g.
          Code:
          Some text [b]containing[/b] code


      NB It is not appropriate to use this markup style in other ways, or to add additional tags to it, without first discussing it, as this may confuse implementations of programs designed to convert Hermitish mark-up to HTML.


    Capitalization Hint

      The use of CAPITALS to demote emphasis is often perceived as being equivalent to shouting and is deprecated.


    Line Wrapping

      It is strongly recommended that text not be line wrapped. This means that it will be readable when placed on web pages, transformed to PDF or viewed on WAP devices. If your mail reader cannot reflow text, obtain a better one, which can do so.


    Full Copyright Statement
    Copyright (C) The Church of Virus (2002).  All Rights Reserved.
    http://www.churchofvirus.com

    This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the Abbreviated Copyright Notice [supra] and this paragraph are included as an inseparable component of all such copies and derivative works, and that the terms of this copyright statement shall be binding on derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Church of Virus, except as needed for the purpose of developing further Church of Virus documents or as required to translate it into languages other than English, in which case the procedures for copyrights defined by the Church of Virus from time to time must be followed.
    The limited permissions granted above are perpetual and will not be revoked by the Church of Virus or its successors or assigns.
    This document and the information contained herein is provided on an "AS IS" basis and the Church of Virus disclaims all warranties, express or implied, including but not limited to any warranty that the use of the information herein will not infringe any rights or any implied warranties of merchantability or fitness for a particular purpose. You are specifically warned that study of documents produced by the Church of Virus may lead to a permanent change in your attitudes or behavior as a result of exposure to the memeplexii and component memes embedded in such documents.

    Acknowledgements
    http://www.yabbforum.com/ for the mark-up format. It is possible that additional formatting markup compliant with “yabb” will be included in later releases of this document.

    Bibliography

    References
    http://www.yabbforum.com/YaBBHelp/posting.html

    Authors’ addresses
    lhermit@hotmail.com
« Last Edit: 2007-12-12 20:35:36 by Hermit » Report to moderator   Logged

With or without religion, you would have good people doing good things and evil people doing evil things. But for good people to do evil things, that takes religion. - Steven Weinberg, 1999
Hermit
Archon
*****

Posts: 4263
Reputation: 8.35
Rate Hermit



Prime example of a practically perfect person

View Profile WWW
Re:FAQ: Hermitish mail mark-up and citation V2.1
« Reply #1 on: 2007-12-12 16:01:54 »
Reply with quote

Given the move away from mail lists, the time seems to have come for a new version.

Hermit
Report to moderator   Logged

With or without religion, you would have good people doing good things and evil people doing evil things. But for good people to do evil things, that takes religion. - Steven Weinberg, 1999
Blunderov
Archon
*****

Gender: Male
Posts: 3160
Reputation: 8.87
Rate Blunderov



"We think in generalities, we live in details"

View Profile WWW E-Mail
Re:FAQ: Hermitish mail mark-up and citation V2.1
« Reply #2 on: 2007-12-12 16:35:20 »
Reply with quote

[Blunderov] Thank you for your work hermit. I will endevour to implement your guidelines.
Report to moderator   Logged
Stringy
Initiate
**

Gender: Male
Posts: 15
Reputation: 5.51
Rate Stringy



Life is a trip...and we got tickets

View Profile WWW E-Mail
Re:FAQ: Hermitish mail mark-up and citation V2.1
« Reply #3 on: 2007-12-12 16:40:50 »
Reply with quote

As will I if ever I can understand them.
Report to moderator   Logged

I'm neither a scientist nor a scholar. I'm, primarily, an entertainer. That does not invalidate my ideas...but it does make them suspect.
Hermit
Archon
*****

Posts: 4263
Reputation: 8.35
Rate Hermit



Prime example of a practically perfect person

View Profile WWW
Re:FAQ: Hermitish mail mark-up and citation V2.1
« Reply #4 on: 2007-12-12 16:48:30 »
Reply with quote

FAQ: Hermitish Mark-up v. 3.0

URL: http://virus.lucifer.com/bbs/index.php?board=31;action=display;threadid=11526

Authors: Hermit

Revision: 3.0B (Full BBS mark-up)

Author’s notes for revision: 3.0
This markup system is now used principally upon the CoV BBS. As such some adaptation has occurred over time, and other improvements suggest themselves. This document release will maintain compatibility with Ver 2.1B The most significant change is in version numbering which transitions from simple sequencing to using BBS reply numbers to refer to previous responses. This dramatically simplifies the process of indexing. It also obsoletes much material surrounding this practice, and in particular the "back quoting" and "Message Index" of the previous version is now obsolete, being handled through the mechanics of the BBS system.
As done previously, but not noted, a technical problem, that the "[ code ]" operator does not work completely reliably to suppress formatting of tags has been addressed in an ad hoc fashion, through adapting the sample tags sufficiently to prevent the system from reacting to them, while still appearing similar to the tag itself. This practice is now identified where it has been used.

In case any one wondered, comments, criticisms and suggestions are requested and welcomed.
It should be noted that the “B” suffixed version of this FAQ (i.e. formatted for BBS display) is authoritative, and that the “A” suffixed version is derived from the “B” suffixed version for the purposes of ASCII email.

Status
The use of this system is recommended but not mandated for postings on the CoV BBS. Using it will make it more likely that others will read your submissions and will help to prevent the CoV from becoming a "write only zone." The use of HTML in posting to the CoV is deprecated and should be avoided under any circumstances.

Abbreviated Copyright Notice
Copyright (C) The Church of Virus, 2002. All rights reserved. Unlimited distribution permitted in accordance with the terms of the Full copyright notice below.

Abstract
This FAQ addresses the issues of mail compatible BBS-markup (formatting), citation, titling and snipping.
A preferred approach to dialog mark-up, permitting easy use with ASCII email, as well as providing “safe” markup for display within systems displaying mail-list comments for access by web-browsers is introduced. In addition, the recommended format permits readers and author’s to follow “threaded-discussions” without difficulty.

Table of Contents
    Title
    Authors
    Revision
    Author’s notes for revision
    Status
    Abbreviated Copyright Notice
    Abstract
    Table of Contents
    Introduction
    Preferred Implementation
      Responsibilities
      Elision (or "snipping")
      Subject Line
      Attribution
      Sequence
      Reference
      Citation
      Dating
      Other Mark-up

        Horizontal line
        Italic text
        Underlined text
        Strikethrough text
        Color text
        Quote text
        Indented list
        Quote code

      Capitalization Hint
      Line Wrapping

    Full copyright notice
    Acknowledgements
    Bibliography
    References
    Authors’ addresses


Introduction
This FAQ is intended to improve the formatting, and referencing of work produced by the members of the Church of Virus, in order to simplify the task of making such works more accessible to the public and other members. In addition, it introduces and documents “Hermitish” threading, a form of conversational threading to allow the easy writing and following of threaded multiperson discussions.

Preferred Implementation


    Responsibilities

      An initial post in a sequence need not be fully marked up (although it may be in order to appear more attractive and in order to relieve respondents of part of the task). The respondent to any post has the responsibility of marking up the original message and their response.
      Subsequent replies and comments on a message already so marked up, have the responsibility of appropriately marking up their reply.
      Each person sending a message has the responsibility of removing artifacts imposed by the system from their messages.

    If a person responding to a message takes long enough over the composition process that somebody else takes the reply number, it is the poster's responsibility to renumber their post. This situation may be avoided by saving a draft copy of the work and then editing it. It is recommended to add a "draft flag" to the start of the document to be removed only when editing is complete.
    Code:
    [color=red][size=6][b]Draft[/b][/size][/color]
    is appropriate, resulting in Draft.
    This allows you to "reserve" a reply number (and save your work in case of power failures or crashes) while warning others not to reply until the "draft" notice is removed.

    Elision (or "snipping")

      When material is omitted from a follow-up post, the omitted material should be denoted by:
      Example:

        <snip>

      It is worth bearing in mind that many people have limited reading speeds and patience, and few want to repeatedly read long posts to see where the replies are located. Please use your judgment in snipping to keep volumes tolerable.

      When <snipping> is desirable

        <snipping> is appropriate when you do not disagree on a point, or
        where you state that a point is not worth arguing. It is also worthwhile when
        replying with a short (or even a long) comment to the gist of a previous post, but where you are discussing the totality not the independent points of the post.

      When <snipping> is not desirable

        Don't <snip> something that you take issue with, or some lamer will attack you for removing their arguments and assert that you did this invalidly because you couldn't argue your case effectively rather than just putting back the excised material.
        <Snipping> is not appropriate when your opponent has made a valid point and you do not acknowledge it.

      This last is also a strong hint to avoid being seen as a lamer. If somebody snips something of yours and you choose to reply, simply put it back in place, and observe on why you think your text should not have been <snipped>. If you feel very strongly about this, you might choose to denote the restored material with <snip restored by NAME>.


    Subject Lines

      To maintain the accessibility and readability of the archives, it is important that you reply on subject. If you intend to change the subject in a post, create a new one in the appropriate forum, give it an appropriate topic and provide a back link to the original discussion in the new document, as well, perhaps, as posting a forward pointer at the end of the old thread.


    Attribution

      Each paragraph is identified by the name of the speaker.
      Example:

        [Hermit] Says something.


    Sequence

      When a sequence of communications occur, this is indicated by a number suffixed to the name of the speaker. The first post on a thread is 0, followed by reply 1 etc. This is performed automatically by the BBS system and should be followed with care. Posts by others that are not quoted, and posts where <Sniping> has occurred on the thread need not have all the numbers in a sequence present, but any numbers present must conform with the BBS reply numbers
      Example:

        [Hermit 0] A implies B.[ <- Note the Use of 0 for the first post in a sequence]
        [Somebody 1] So is B True?
        [Hermit 2] Only if A is True.
        [Somebody 4]How do I know this? [Note skipped number - perhaps somebody else's post]
        [Hermit 5] Perhaps because it was previously stated:
        [ur1=http://www.churchofvirus.org/bbs/index.php?board=4;action=display;threadid=36595;start=15]  [ Church of Virus BBS, General, Church Doctrine, exploring religious thinking, Reply #16 on 2007-12-12, Hermit ] [/ur1] Yadda, yadda, yadda

    NB "url" is replaced by "ur1" (last character lower-case L swapped by numeric 1)  in the above example simply to show how this may be achieved.

    Reference

      In order to refer to a particular statement a decimal may be suffixed to the reply number.
      Example:

        [Hermit 1] Yada, Yada, Yada...
        [Hermit 2.5]  I refer to "some useful reference" which says X.
        [Hermit 2] Yada, Yada, Yada...
        [Somebody 3] I don't think that "some useful reference" is really useful.
        [Hermit 4] But in [Hermit 2.5] I have already provided a reference you can check for yourself.
        [Somebody 5] Yada, Yada, Yada

      It is not necessary to number each paragraph, simply add reference numbers when and where needed – to your own, or anyone else’s posts. When reference numbers are added to a post, they must be done so in sequence. It is always possible to insert a new reference when required by adding another level of decimal.
      Example:

        [Hermit 1.1] existing
        [Hermit 1.15] <--- inserted reference.
        [Hermit 1.2] existing


    Citation

      To refer to a previous post on the CoV BBS, cite it as e.g.:
      [ur1=http://www.churchofvirus.org/bbs/index.php?board=4;action=display;threadid=36595;start=15]  [ Church of Virus BBS, General, Church Doctrine, exploring religious thinking, Reply #16 on 2007-12-12, Hermit ] [/ur1] resulting in a link appearing as   [ Church of Virus BBS, General, Church Doctrine, exploring religious thinking, Reply #16 on 2007-12-12, Hermit ]

      NB "url" is replaced by "ur1" (last character lower-case L swapped by numeric 1)  in the above example simply to show how this may be achieved.

      If you have a web link, cite it as follows:
      Cite a post with a text description:

        [ur1=http://site.com/pointer to archive item]"Subject Line", Author, Sent Time[/ur1]


      NB "url" is replaced by "ur1" (last character lower-case L swapped by numeric 1)  in the above example simply to show how this may be achieved.

      This allows a post to be found in a large number of ways and prevents the confusion of which post in a sequence sharing a subject line and with multiple participants is actually meant.
      Example:
      or just Cite a post by URL if the post is identified elsewhere in the message:

        [ur1]http://forum.javien.com/XMLmessage.php?id=id::XERAICIg-AhZq-AGI4-DSAO-LyUrYEBwG1Zu[/ur1]

      Example:


    NB "url" is replaced by "ur1" (last character lower-case L swapped by numeric 1)  in the above example simply to show how this may be achieved.

    Web URL Citation

      Optionally, when citing a web page, affix a date so that others may see when it was last accessed.
      Cite a URL with a text description:

        [ur1=http://virus.lucifer.com]some hyperlinked text accessed 2002-02-01[/ur1]

      Example:
      Or, citing a URL without a text description:

        [ur1]http://virus.lucifer.com[/ur1] accessed 2002-02-01

      Example:

      NB "url" is replaced by "ur1" (last character lower-case L swapped by numeric 1)  in the above example simply to show how this may be achieved.

      Where the last access was on the date the document was written, the inclusion of the access date is unnecessary. Thus if no access date is provided the assumption is that the access was on the day the post was made. In which case citing a URL citing a URL without a text description:

        [ur1]http://virus.lucifer.com[/ur1]

      Example:
      is appropriate.

      NB "url" is replaced by "ur1" (last character lower-case L swapped by numeric 1)  in the above example simply to show how this may be achieved.

      To include a reference to an image:

        [ img]http://virus.lucifer.com/images/cov.gif[/ img]

      Example:



      NB "img" is replaced by " img" (an additional space is added preceding the code)  in the above example simply to show how this may be achieved.

      To include a reference to a flash image:

        [f1ash=200,200]URL[/f1ash]

      Example:



      NB "flash" is replaced by "f1ash" (second character lower-case L swapped by numeric 1)  in the above example simply to show how this may be achieved.



      NB "email" is replaced by "emai1" (last character lower-case L swapped by numeric 1)  in the above example simply to show how this may be achieved.

        To include a reference to a Virian:

          [ur1=http://www.churchofvirus.org/bbs/index.php?board=4;action=viewprofile;user=Hermit]Hermit[/ur1]

        Example:


      NB "url" is replaced by "ur1" (last character lower-case L swapped by numeric 1)  in the above example simply to show how this may be achieved.

        To include a reference to a Book (via Amazon):

          [ur1]http://www.amazon.com/exec/obidos/ASIN/ISBN here/thechurchofvirusA[/ur1]

        or

          [ur1]http://www.amazon.com/exec/obidos/ASIN/ISBN here/thechurchofvirusA]Title, Author, Publisher, Date[/ur1]

        In either case inserting the ISBN of the book where it says "ISBN here" to refer to specific books. The ISBN is sometimes referred to by Amazon as the ASN or ASIN of a book and can always be found on the page dealing with the book at Amazon. or, if you don't see it there, in the URL of the page about the book.

        NB "url" is replaced by "ur1" (last character lower-case L swapped by numeric 1)  in the above examples, simply to show how this may be achieved.

        Example:
        or


      For each purchase made by people using this link format, the CoV will receive a small percentage of the selling price.


      Dating

        We recommend the use of the ISO 601 date format which has the following structure: YYYY-MM-DD HH:MM[:SS] [TIMEZONE]. (Refer Status for Date and Time Formats). This automatically sorts things so dated into an appropriate time sequence and allows easy date lookups. Seconds and the time zone may be omitted if unimportant. It is in any case recommended that Universal (i.e. Zulu) time always be used to avoid confusion.


      Other Mark-up

        Aside from sniping ("<snip>") It is recommended that XML/HTML style bracketing be avoided, to prevent confusing existing embedding of messages from the CoV into web pages, but that square brackets, i.e. "[" and "]" be used instead.

        The following are appropriate codes:
        Draw a horizontal line:

          Code:
          [hr]

          e.g.

        Use Bold Text:

          Code:
          [b]Bold[/b]

          e.g. Bold


        Use Italic Text:

          Code:
          [i]Italic[/i]

          e.g. Italic


        Use Underline Text:

          Code:
          [u]Underlined[/u]

          e.g. Underlined


        Use Strikethrough Text:

          Code:
          [s]strikethrough[/s]

          e.g. strikethrough


        Use Color text (e.g. Red):

          Code:
          [color=Red]Red text[/color]

          e.g. Red text


        Quote text:

          Code:
          [quote]Quoted text[/quote]

          e.g.
          Quote:
          Quoted text


        Form an indented list:

          Code:

          [list]some list
          more list
          last list[/list]

          e.g.
            some list
            more list
            last list


        Cite “Code”, i.e. show the value of tags rather than performing the function of the code.

          Code:
          [ code]Some text [b]containing[/b] code[/ code]

          e.g.
          Code:
          Some text [b]containing[/b] code


      NB "code" is replaced by " code" (a leading blank is inserted before the tag) in the above example simply to show how this may be achieved.

      NB It is not appropriate to use this markup style in other ways, or to add additional tags to it, without first discussing it, as this may confuse implementations of programs designed to convert Hermitish mark-up to HTML.


    Capitalization Hint

      The use of CAPITALS to demote emphasis is often perceived as being equivalent to shouting and is deprecated.


    Line Wrapping

      It is strongly recommended that text not be line wrapped. This means that it will be readable when placed on web pages, transformed to PDF or viewed on WAP devices. If your mail reader cannot reflow text, obtain a better one, which can do so.


    Full Copyright Statement
    Copyright (C) The Church of Virus (2002).  All Rights Reserved.
    http://www.churchofvirus.com

    This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the Abbreviated Copyright Notice [supra] and this paragraph are included as an inseparable component of all such copies and derivative works, and that the terms of this copyright statement shall be binding on derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Church of Virus, except as needed for the purpose of developing further Church of Virus documents or as required to translate it into languages other than English, in which case the procedures for copyrights defined by the Church of Virus from time to time must be followed.
    The limited permissions granted above are perpetual and will not be revoked by the Church of Virus or its successors or assigns.
    This document and the information contained herein is provided on an "AS IS" basis and the Church of Virus disclaims all warranties, express or implied, including but not limited to any warranty that the use of the information herein will not infringe any rights or any implied warranties of merchantability or fitness for a particular purpose. You are specifically warned that study of documents produced by the Church of Virus may lead to a permanent change in your attitudes or behavior as a result of exposure to the memeplexii and component memes embedded in such documents.

    Acknowledgements
    http://www.yabbforum.com/ for the mark-up format. It is possible that additional formatting markup compliant with “yabb” will be included in later releases of this document.

    Bibliography

    References
    http://www.yabbforum.com/YaBBHelp/posting.html

    Authors’ addresses
    hermit@lucifer.com
« Last Edit: 2007-12-13 05:18:07 by Hermit » Report to moderator   Logged

With or without religion, you would have good people doing good things and evil people doing evil things. But for good people to do evil things, that takes religion. - Steven Weinberg, 1999
Stringy
Initiate
**

Gender: Male
Posts: 15
Reputation: 5.51
Rate Stringy



Life is a trip...and we got tickets

View Profile WWW E-Mail
Re:FAQ: Hermitish mail mark-up and citation V2.1
« Reply #5 on: 2007-12-12 20:15:18 »
Reply with quote

"The use of CAPITALS to demote emphasis is often perceived as being equivalent to shouting and is depreciated."

Perhaps it is deliberate? but I think you mean deprecated?
Report to moderator   Logged

I'm neither a scientist nor a scholar. I'm, primarily, an entertainer. That does not invalidate my ideas...but it does make them suspect.
Hermit
Archon
*****

Posts: 4263
Reputation: 8.35
Rate Hermit



Prime example of a practically perfect person

View Profile WWW
Re:FAQ: Hermitish mail mark-up and citation V2.1
« Reply #6 on: 2007-12-12 20:39:52 »
Reply with quote

I do indeed.

Thank-you

Hermit
Report to moderator   Logged

With or without religion, you would have good people doing good things and evil people doing evil things. But for good people to do evil things, that takes religion. - Steven Weinberg, 1999
Hermit
Archon
*****

Posts: 4263
Reputation: 8.35
Rate Hermit



Prime example of a practically perfect person

View Profile WWW
Useful request note and hint on URL Formatting
« Reply #7 on: 2009-08-06 20:47:50 »
Reply with quote

Please bracket your last cited URL with
Quote:
[ url ] [ /url ]
resulting in http://... or even better, add a short name like this
Quote:
[ url=http://SomeInsanelyLongURL.whatever ] ShortURL [ /url ]
resulting in ShortURL (in both cases leave out the spaces I inserted to force the BBS to let you see the required labels) in order to allow it to be clicked on and to rescue the page from having to be scrolled. This request will then be deleted.
Report to moderator   Logged

With or without religion, you would have good people doing good things and evil people doing evil things. But for good people to do evil things, that takes religion. - Steven Weinberg, 1999
Pages: [1] Reply Notify of replies Send the topic Print 
Jump to:


Powered by MySQL Powered by PHP Church of Virus BBS | Powered by YaBB SE
© 2001-2002, YaBB SE Dev Team. All Rights Reserved.

Please support the CoV.
Valid HTML 4.01! Valid CSS! RSS feed