Guide for HTML / PDF

                            

Table of Contents:

1. Introduction:

1.1. Purpose
1.2. Transitional and Strict

2. General Considerations:

2.1. HTML Flavors
2.2. Server-Side Files
2.3. Extraction Techniques
2.4. Including Escaped Markup
2.5. Scope of Extraction
2.6. Order of Extraction
2.7. Identifiers
2.8. Preserving Attribute Values
2.9. Non-HTML Content
2.10. CDATA Sections
2.11. Multilingual Documents
2.12. Entity References
2.13. Numeric Character References
2.14. Comments
2.15. Processing Instructions
2.16. White Spaces

3. General Structure:

3.1. Mapping HTML Elements
3.2. Mapping HTML Attributes

4. Details by Element and Attribute:

4.1. Inline Elements
4.2. <meta> Element
4.3. <img> Element
4.4. SVG Images
4.5. <object> and <param> Elements
4.6. HTML Forms
4.7. XForms Forms
4.8. Bidirectional Markers
4.9. <br> Element
4.10. Languages Switch
4.11. Pre-formatted Content
4.12. Script Content
4.13. Style Content

        ----------------------------------------------------------------

                                                 

Sample of the pdf document : 

1. Introduction:

As different tools may provide different filters to extract the content of HTML documents it is important for interoperability that they represent the extracted data in identical manner in the XLIFF document.

1.1. Purpose:
The intent of this document is to provide a set of guidelines to represent HTML data in XLIFF. It offers a collection of recommended mapping of the HTML elements and attributes developers of XLIFF filters can implement, and users of XLIFF utilities can rely on to insure a better interoperability between tools.




1.2 Transitional and Strict:

XLIFF is specified in two "flavors". Indicate which of these variants you are using by selecting the appropriate schema.

The schema may be specified in the XLIFF document itself or in an OASIS catalog. The namespace is the same for both variants. Thus, if you want to validate the document, the tool used knows which variant you are using. Each variant has its own schema that defines which elements and attributes are allowed in certain circumstances.

As newer versions of XLIFF are approved, sometimes changes are made that render some elements, attributes or constructs in older versions obsolete. Obsolete items are deprecated and should not be used even though they are allowed. The XLIFF specification details which items are deprecated and what new constructs to use.


● Transitional - Applications that produce older versions of XLIFF may still use deprecated items. Use this variant to validate XLIFF documents that you read. Deprecated elements and attributes are allowed.

xsi:schemaLocation='urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd'

● Strict - All deprecated elements and attributes are not allowed. Obsolete items from previous versions of XLIFF are deprecated and should not be used when writing new XLIFF documents......




                                                 Click here for  Download PDF / FREE