archive-gr.com » GR » T » TEIPIR.GR

Total: 878

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • EFF's (Extended) Guide to the Internet - Commands and Tools
    name mode mode channel p mode channel s nick query quit signoff Subject Re j summon topic who 60 chan 62 whois whowas post a ARC ARCE archie archie s filename b BinHex c cat cd compress cp d dos2unix e elm emacs f ftp ftp site name FTP bin FTP binary FTP cd FTP cdup FTP dir FTP get FTP ls FTP mget FTP prompt ftpmail g gopher gunzip

    Original URL path: http://web.teipir.gr/eegtti/eeg_302.html (2016-02-14)
    Open archived version from archive

  • EFF's (Extended) Guide to the Internet - General Index
    FBI Federal Bureau of Investigation FCC Federal Communications Commission FEDIX Fidonet Fish Flame Flame war Flamer Fortune cookie Free Net FTP FTP mail by FTP ncftp g Gaffin Adam Gaskin Stephen Gates Bill Gateway GEnie GhostScript Gibson William GIF Gilmore John Glickman Matt Global community Global village Glover Chris GNU Goehring Scott Good Thing Gopher Gopher bookmark Greatful Dead Gumprecht Blake Gutenberg s Bible h Hacker Hacker Crackdown Hardy Henry E Heelan Bill Heitkötter Jörg Hewlett Packard Corp Hiroshima Holocaust Holonet Holy war Hong Kong Horton Mark Host Host system HyperCard Hytelnet i IBM IMHO IndianNet Indians Information highway International Business Machines Corp Internet Relay Chat Internet worm IRC ISDN Integrated Services Digital Network ISOC j Jackson David S Jackson Steve Jughead Junk mail Jupiter k K12Net Kahn Philippe Kamens Jonathan I Kaminski Peter Kapor Mitchell Kehoe Brendan P Kennedy Khrushchev Killfile King Wendy KIS Knowbot Information Service Knoxville News Sentinel Online KNSO Koran l Landweber Lawrence H Lenin Lewis Carroll Linux Listserver Lost in Space Lotus Development Corp Lurker m Macintosh Macintosh software Magna Carta Mailbox Mailing list Mailing list Moderator Mailing list subscribe Mailing list unsubscribe Manners Miss Manutius Aldus Manzi Jim Marillion Mark Twain Markoff John mbox file McCandlish Stanton MCIMail MCM Macintosh Communications Forum Mercury Freddie Michnet MicroMUSE Microsoft Windows Microsoft Corp MIME Multi purpose Internet Mail Extensions Mirror site MIT Press Modem Modem tax Modem 2400 baud Modem Hayes compatible Modem high speed Modem tax Modulator MOLIS Morris Robert MS DOS MTV MUD Multiple User Dimensions Multiple User Dungeons n NAP Network Access Point NASA National Science Foundation Native Americans Net character Net citizen Net effect Net geek Net god Net nazi Net saint Net speak Net surfer Net weenie NetBSD Netcom Neuromancer News resource file NewsBytes Newsroom NeXT NeXT Step NovX NREN NSF NSFnet

    Original URL path: http://web.teipir.gr/eegtti/eeg_303.html (2016-02-14)
    Open archived version from archive

  • Introduction to HTML 3.0
    features HTML 3 0 is designed but doesn t require to be used together with style sheets which give rich control over document rendering and can take into account the user s preferences the window size and other resource limitations such as which fonts are actually available This work will eventually lead to smart layout under the author s control with rich magazine style layouts for full screen viewing switching to simpler layouts when the window is shrunk The SGML Open consortium is promoting use of DSSSL Lite by James Clark This is a simplified subset of DSSSL the document style semantics specification language DSSSL is a ISO standard for representing presentation semantics for SGML documents but is much too complex in its entirety to be well suited to the World Wide Web Håkon Lie maintains a list of pointers to work on style sheets Transition Strategy from HTML 2 0 The use of the MIME content type text html version 3 0 is recommended to prevent existing HTML 2 0 user agents screwing up by attempting to show 3 0 documents Tests have shown that the suggested content type will safely cause existing user agents to display the save to file dialog rather than incorrectly displaying the document as if it were HTML 2 0 To make it easy for servers to distinguish 3 0 documents from 2 0 documents it is suggested that 3 0 files are saved with the extension html3 or ht3 for PCs Servers can also exploit the accept headers in HTTP requests from HTML user agents to distinguish whether each client can or cannot support HTML 3 0 This makes it practical for information providers to start providing HTML 3 0 versions of existing documents for newer user agents without impacting older user agents It is envisaged that programs will be made available for automatic down conversion of 3 0 to 2 0 documents This conversion could be carried out in batch mode or on the fly with caching for greater efficiency Design Guidelines The HTML 3 0 draft specification has been written to the following guidelines Lingua Franca for the Web HTML is intended as a common medium for tying together information from widely different sources A means to rise above the interoperability problems with existing document formats and a means to provide a truly open interface to proprietary information systems Simplicity The first version of HTML was designed to be extremely simple both to author and to write browsers for This has played a major role in the incredibly rapid growth of the World Wide Web HTML 3 0 provides a clean superset of HTML 2 0 adding high value features such as tables text flow around figures and math while still remaining a simple document format The pressures to adopt the complexities of traditional SGML applications has been resisted for example the Department of Defense s CALS table model or the ISO 12083 math DTD Scaleability As time goes by people

    Original URL path: http://web.teipir.gr/HTML_3.0/intro.html (2016-02-14)
    Open archived version from archive

  • Understanding HTML and MIME
    text html The type text html accepts the following parameters Version To help avoid future compatibility problems the version parameter may be used to give the version number of the specification to which the document conforms The version number appears at the front of this document and within the public identifier for the SGML DTD This specification defines version 3 0 Character sets The charset parameter as defined in section 7 1 1 of RFC 1521 may be used with the text html content type to specify the encoding used to represent the HTML document as a sequence of bytes Normally text media types specify a default of US ASCII for the charset parameter However for text html if the byte stream contains data that is not in the 7 bit US ASCII set the HTML interpreting agent should assume a default charset of ISO 8859 1 When an HTML document is encoded using US ASCII the mechanisms of numeric character references and character entity references may be used to encode additional characters from ISO 8859 1 Character entity references are needed for symbols such as math and greek characters from other unspecified character sets Other values for the charset

    Original URL path: http://web.teipir.gr/HTML_3.0/HTMLandMIME.html (2016-02-14)
    Open archived version from archive

  • Understanding HTML and SGML
    support for these idioms is widely deployed their use is strongly discouraged Names The element name immediately follows the tag open delimiter An element name consist of a letter followed by up to 72 letters digits periods or hyphens Names are not case sensitive For example H1 is equivalent to h1 This limit of 72 characters is set by the NAMELEN parameter in the SGML declaration for HTML 3 0 Attributes In a start tag white space and attributes are allowed between the element name and the closing delimiter An attribute typically consists of an attribute name an equal sign and a value although some attributes may be just a value White space is allowed around the equal sign The value of the attribute may be either A string literal delimited by single quotes or double quotes A name token a sequence of letters digits periods or hyphens In this example a is the element name href is the attribute name and http host dir file html is the attribute value A HREF http host dir file html Some implementations consider any occurrence of the character to signal the end of a tag For compatibility with such implementations when appears in an attribute value you may want to represent it with an entity or numeric character reference such as IMG SRC eq1 ps alt a 62 b To put quotes inside of quotes you can use single quotes if the outer quotes are double or vice versa as in IMG SRC image ps alt First real example Alternatively you use the character representation quot as in IMG SRC image ps alt First quot real quot example The length of an attribute value after replacing entity and numeric character references is limited to 1024 characters This number is defined by the LITLEN parameter in the SGML declaration for HTML 3 0 Note Some implementations allow any character except space or in a name token Attributes values must be quoted only if they don t satisfy the syntax for a name token Attributes with a declared value of NAME e g ISMAP COMPACT may be written using a minimized syntax The markup UL COMPACT compact can be written as UL COMPACT Note Unless you use the minimized syntax some implementations won t understand Undefined Tag and Attribute Names It is an accepted networking principle to be conservative in that which one produces and liberal in that which one accepts HTML parsers should be liberal except when verifying code HTML generators should generate strictly conforming HTML It is suggested that where ever practical parsers should at least flag the presence of markup errors as this will help to avoid bad markup being produced inadvertently The behavior of WWW applications reading HTML documents and discovering tag or attribute names which they do not understand should be to behave as though in the case of a tag the whole tag had not been there but its content had or in the case of an attribute

    Original URL path: http://web.teipir.gr/HTML_3.0/HTMLandSGML.html (2016-02-14)
    Open archived version from archive

  • The Structure of HTML 3.0 Documents
    identify the document as being HTML 3 0 it is recommended that documents start with the prologue doctype HTML public W3O DTD W3 HTML 3 0 EN When absent this prologue is implied by the MIME content type for HTML 3 0 together with the associated version parameter Document Structure HTML 3 0 documents formally have the following structure HTML HEAD head elements BODY body elements HTML In most cases the HTML HEAD and BODY tags can be safely omitted Note that the formal syntax of HTML 3 0 is defined by the document type definition which is included as an appendix of this specification The details of the HEAD and BODY elements will be described in subsequent sections The permitted syntax of HTML 3 0 compliant documents is specified by the DTD This includes the content model for each element defining what markup is permitted within each element The DTD uses SGML entities in content models to express regular features of HTML 3 0 for example body content defines what markup is permitted within the BODY element A number of other elements also share this content model e g BQ DIV FORM TH and TD The description of each tag includes the content model and the permitted context which elements can contain this tag Where practical these properties are given with the same entity names as used in the DTD and should help the newcomer to get to grips with understanding the DTD itself For example the description of the NOTE element starts with The NOTE element Permitted context block Content model flow This says that the NOTE element used for admonishments such as notes cautions and errors can occur in any element which includes block in its content model Similarly any element with flow as part of its

    Original URL path: http://web.teipir.gr/HTML_3.0/overview.html (2016-02-14)
    Open archived version from archive

  • The Head Element and Related Elements
    be defined in each document and provide a means for orienting users in extended documents An example of toolbar LINK elements LINK REL Previous HREF doc31 html LINK REL Next HREF doc33 html LINK REL Bookmark TITLE Order Form HREF doc56 html Using LINK to include a Document Banner The LINK element can be used with REL Banner to reference another document to be used as banner for this document This is typically used for corporate logos navigation aids and other information which shouldn t be scrolled with the rest of the document For example LINK REL Banner HREF banner html The use of a LINK element in this way allows a banner to be shared between several documents with the benefit of being able to separately cache the banner Rather than using a linked banner you can also include the banner in the document itself using the BANNER element Link to an associated Style Sheet The LINK element can be used with REL StyleSheet to reference a style sheet to be used to control the way the current document is rendered For example LINK REL StyleSheet HREF housestyle dsssl Other uses of the LINK element Additional relationship names have been proposed but do not form part of this specification Servers may also allow links to be added by those who do not have the right to alter the body of a document META The META element is used within the HEAD element to embed document meta information not defined by other HTML elements Such information can be extracted by servers clients for use in identifying indexing and cataloging specialized document meta information Although it is generally preferable to used named elements that have well defined semantics for each type of meta information such as title this element is provided for situations where strict SGML parsing is necessary and the local DTD is not extensible In addition HTTP servers can read the contents of the document head to generate response headers corresponding to any elements defining a value for the attribute HTTP EQUIV This provides document authors with a mechanism not necessarily the preferred one for identifying information that should be included in the response headers of an HTTP request The META element has three attributes NAME Used to name a property such as author publication date etc If absent the name can be assumed to be the same as the value of HTTP EQUIV CONTENT Used to supply a value for a named property HTTP EQUIV This attribute binds the element to an HTTP response header If the semantics of the HTTP response header named by this attribute is known then the contents can be processed based on a well defined syntactic mapping whether or not the DTD includes anything about it HTTP header names are not case sensitive If absent the NAME attribute should be used to identify this meta information and it should not be used within an HTPP response header Examples If the document contains META

    Original URL path: http://web.teipir.gr/HTML_3.0/dochead.html (2016-02-14)
    Open archived version from archive

  • The Body Element and Related Elements
    NAME tokens and must be unique within the scope of the current document LANG This is one of the ISO standard language abbreviations e g en uk for the variation of English spoken in the United Kingdom It can be used by parsers to select language specific choices for quotation marks ligatures and hypenation rules etc The language attribute is composed from the two letter language code from ISO 639 optionally followed by a period and a two letter country code from ISO 3166 CLASS This a space separated list of SGML NAME tokens and is used to subclass tag names For instance P CLASS STANZA COUPLET defines a paragraph that acts as a couplet in a stanza By convention the class names are interpreted hierarchically with the most general class on the left and the most specific on the right where classes are separated by a period The CLASS attribute is most commonly used to attach a different style to some element but it is recommended that where practical class names should be picked on the basis of the element s semantics as this will permit other uses such as restricting search through documents by matching on element class names The conventions for choosing class names are outside the scope of this specification BACKGROUND This can be used to specify a URI for an image tile to cover the document background This provides a way of giving a group of documents a distinctive appearence Clients may ignore this attribute It is included here for the benefit of clients that don t support style sheets Note that the text color may need to be adjusted to show an adequate contrast with the background Note that you don t need to include a BODY tag unless you want to specify one

    Original URL path: http://web.teipir.gr/HTML_3.0/docbody.html (2016-02-14)
    Open archived version from archive



  •