Translate Toolkit Documentation Release 2.5.1

Total Page:16

File Type:pdf, Size:1020Kb

Translate Toolkit Documentation Release 2.5.1 Translate Toolkit Documentation Release 2.5.1 Translate.org.za Apr 25, 2020 Contents 1 User’s Guide 3 1.1 Features..................................................3 1.2 Installation................................................4 1.3 Converters................................................6 1.4 Tools................................................... 61 1.5 Scripts.................................................. 100 1.6 Use Cases................................................. 112 1.7 Translation Related File Formats..................................... 129 2 Developer’s Guide 163 2.1 Translate Styleguide........................................... 163 2.2 Documentation.............................................. 170 2.3 Building................................................. 173 2.4 Testing.................................................. 174 2.5 Command Line Functional Testing................................... 176 2.6 Contributing............................................... 178 2.7 Translate Toolkit Developers Guide................................... 180 2.8 Making a Translate Toolkit Release................................... 184 2.9 Deprecation of Features......................................... 189 3 Additional Notes 191 3.1 Release Notes.............................................. 191 3.2 History of the Translate Toolkit..................................... 231 3.3 License.................................................. 233 4 API Reference 235 4.1 API.................................................... 235 Python Module Index 705 Index 709 i ii Translate Toolkit Documentation, Release 2.5.1 Welcome to Translate Toolkit’s documentation. This documentation covers both user’s and programmer’s perspective. Contents 1 Translate Toolkit Documentation, Release 2.5.1 2 Contents CHAPTER 1 User’s Guide This part has the user’s documentation for the tools included in the Translate Toolkit. 1.1 Features • Work with ONE localisation format. You’ll no longer be editing DTD files in one tool, .properties in another, OpenOffice GSI in a third. Simply do all your localisation in a PO or XLIFF editor • Converters for a number of formats – OpenOffice.org SDF/GSI – Mozilla: .properties, DTD, XHTML, .inc, .ini, etc – Others: Comma Separated Value, TMX, XLIFF, TBX, PHP, WordFast TXT, Qt .ts, txt, .ini, Windows .rc, ical, subtitles, Mac OS X strings • File access to localization files through the format API in all the above formats, as well as .qph, .qm, .mo • Output valid target file types. We make sure that your output files (e.g. .properties) contain all comments from the original file and preserves the layout of the original as far as possible. If your PO entry is marked as fuzzy we use the English text, not your half complete translation. The converters for OpenOffice.org and Mozilla formats will also perform simple checks and corrections to make sure you have none of those hard to find localisation bugs. • Our checker has over 42 checks to find errors such as: missing or translated variables, missing accelerator keys, bad escaping, start capitalisation, missing sentences, bad XML and much more. • Language awareness, taking language conventions for capitalisation, quotes and other punctuation into account • Find conflicting translations easily, cases where you have translated a source word differently or used a target word for 2 very different English concepts • Extract messages using simple text or a regular expression allowing you to quickly find and extract words that you need to fix due to glossary changes. • Merge snippets of PO files into your existing translations. 3 Translate Toolkit Documentation, Release 2.5.1 • Create word, string and file counts of your files. Making it much easier to budget time as string counts do not give you a good indication of expected work. • Create a set of PO files with debugging entries to allow you to easily locate the source of translations. Very use- ful in OpenOffice.org which provides scant clues as to where the running application has sourced the message. The Translate Toolkit is also a powerful API for writing translation and localisation tools, already used by our own and several other projects. See the base class section for more information. 1.2 Installation This is a guide to installing the Translate Toolkit on your system. If the Translate Toolkit is already packaged for your system, this is probably the easiest way to install it. For several Linux distributions, the package might be available through your package manager. On Windows, we recommend using a virtual environment. If your system already has the toolkit prepackaged, then please let us know what steps are required to install it. 1.2.1 Building For build instructions, see the Building page. 1.2.2 Download Download a stable released version. Or if you have a python environment, run pip install translate-toolkit. For those who need problems fixed, or who want to work on the bleeding edge, get the latest source from Git. If you install through your distribution’s package manager, you should automatically have all the dependencies you need. If you are installing a version from Version Control, or from a source release, you should check the README file for information on the dependencies that are needed. Some of the dependencies are optional. The README file documents this. 1.2.3 Installing packaged versions Get the package for your system: RPM If you want to install easily on an RPM based system .tar.gz for source based installing on Linux .deb for Debian GNU/Linux (etch version) The RPM package can be installed by using the following command: $ rpm -Uvh translate-toolkit-1.0.1.rpm To install a tar.bz2: $ tar xvjf translate-toolkit-1.1.0.tar.bz2 $ cd translate-toolkit-1.1.0 $ su $ ./setup.py install On Debian (if you are on etch), just type the following command: 4 Chapter 1. User’s Guide Translate Toolkit Documentation, Release 2.5.1 $ aptitude install translate-toolkit If you are using an old Debian stable system, you might want to install the .tar.bz2 version. Be sure to install python and python development first with: $ apt-get install python python-dev Alternatively newer packages might be in testing. 1.2.4 Installing on Windows On Windows we recommend that you install Translate Toolkit using a virtual environment. This makes installation clean and isolated. Use the latest Python 2.7 (at least Python 2.7.9 or newer as it bundles the pip installer). Install virtualenvwrapper-win to simplify handling of virtualenvs. 1. Install latest Python 2.7 2. Open cmd.exe or similar 3. pip install virtualenvwrapper-win 4. mkvirtualenv ttk where “ttk” is the name for the new virtualenv 5. pip install translate-toolkit to install latest stable or pip install –pre translate-toolkit to try a pre-release 6. pip install lxml>=3.5 to be able to use XLIFF or other XML formats 7. po2prop –version to double check you have the right version Next times you need to use Translate Toolkit just remember to: 1. Open cmd.exe or similar 2. workon ttk to enable the virtualenv again 3. Run the Translate Toolkit commands you want 1.2.5 Installing from Git If you want to try the bleeding edge, or just want to have the latest fixes from a stabilising branch then you need to use Git to get your sources: $ git clone https://github.com/translate/translate.git This will retrieve the master branch of the Toolkit. Further Git instructions are also available. Once you have the sources you have two options, a full install: $ su $ ./setup.py install or, running the tools from the source directory: $ su $ pip install -e . 1.2. Installation 5 Translate Toolkit Documentation, Release 2.5.1 1.2.6 Verify installed version To verify which version of the toolkit you have installed run: $ prop2po --version prop2po 2.5.1 1.2.7 Cleaning up existing installation To remove old versions of the toolkit which you might have installed without a virtual environment or without your package manager. The following advice only applies to manual installation from a tarball. 1. Find location of your python packages: $ python -c "from distutils.sysconfig import get_python_lib; print(get_python_ ,!lib())" 2. Delete toolkit package from your Python site-packages directory e.g.: $ rm -R /usr/local/lib/python2.7/dist-packages/translate 1.3 Converters 1.3.1 General Usage The tools follow a general usage convention which is helpful to understand. Input & Output The last two arguments of your command are the input and output files/directories: moz2po<input><output> You can of course still use the -i and -o options which allows you to reorder commands moz2po-o<output>-i<input> Error Reporting All tools accept the option --errorlevel. If you find a bug, add this option and send the traceback to the develop- ers. moz2po<other-options>--errorlevel=traceback Templates If you are working with any file format and you wish to preserve comments and layout then use your source file as a template. 6 Chapter 1. User’s Guide Translate Toolkit Documentation, Release 2.5.1 po2dtd-t<source-file><input><output> This will use the files in <source-file> as a template, merge the PO files in <input>, and create new DTD files in <output> If you ran this without the templates you would get valid DTD files but they would not preserve the layout or all the comments from the source DTD file The same concept of templates is also used when you merge files. pomerge-t<old><fixes><new> This would take the <old> files merge in the <fixes> and output new PO files, preserving formatting, into <new>. You can use the same directory for <old> and <new> if you want the merges to overwrite files in <old>. source2target The converters all follow this convention: • source = the format from which you are converting e.g. in oo2po we are converting from OpenOffice.org SDF/GSI • target = the format into which you are converting e.g. in oo2po we are converting to Gettext PO Getting Help The --help option will always list the available commands for the tool. moz2po--help 1.3.2 moz2po moz2po converts Mozilla files to PO files. It wraps converters that handle .properties, .dtd and some strange Mozilla files.
Recommended publications
  • ABBREVIATIONS EBU Technical Review
    ABBREVIATIONS EBU Technical Review AbbreviationsLast updated: January 2012 720i 720 lines, interlaced scan ACATS Advisory Committee on Advanced Television 720p/50 High-definition progressively-scanned TV format Systems (USA) of 1280 x 720 pixels at 50 frames per second ACELP (MPEG-4) A Code-Excited Linear Prediction 1080i/25 High-definition interlaced TV format of ACK ACKnowledgement 1920 x 1080 pixels at 25 frames per second, i.e. ACLR Adjacent Channel Leakage Ratio 50 fields (half frames) every second ACM Adaptive Coding and Modulation 1080p/25 High-definition progressively-scanned TV format ACS Adjacent Channel Selectivity of 1920 x 1080 pixels at 25 frames per second ACT Association of Commercial Television in 1080p/50 High-definition progressively-scanned TV format Europe of 1920 x 1080 pixels at 50 frames per second http://www.acte.be 1080p/60 High-definition progressively-scanned TV format ACTS Advanced Communications Technologies and of 1920 x 1080 pixels at 60 frames per second Services AD Analogue-to-Digital AD Anno Domini (after the birth of Jesus of Nazareth) 21CN BT’s 21st Century Network AD Approved Document 2k COFDM transmission mode with around 2000 AD Audio Description carriers ADC Analogue-to-Digital Converter 3DTV 3-Dimension Television ADIP ADress In Pre-groove 3G 3rd Generation mobile communications ADM (ATM) Add/Drop Multiplexer 4G 4th Generation mobile communications ADPCM Adaptive Differential Pulse Code Modulation 3GPP 3rd Generation Partnership Project ADR Automatic Dialogue Replacement 3GPP2 3rd Generation Partnership
    [Show full text]
  • XML for Java Developers G22.3033-002 Course Roadmap
    XML for Java Developers G22.3033-002 Session 1 - Main Theme Markup Language Technologies (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Course Roadmap Consider the Spectrum of Applications Architectures Distributed vs. Decentralized Apps + Thick vs. Thin Clients J2EE for eCommerce vs. J2EE/Web Services, JXTA, etc. Learn Specific XML/Java “Patterns” Used for Data/Content Presentation, Data Exchange, and Application Configuration Cover XML/Java Technologies According to their Use in the Various Phases of the Application Development Lifecycle (i.e., Discovery, Design, Development, Deployment, Administration) e.g., Modeling, Configuration Management, Processing, Rendering, Querying, Secure Messaging, etc. Develop XML Applications as Assemblies of Reusable XML- Based Services (Applications of XML + Java Applications) 2 1 Agenda XML Generics Course Logistics, Structure and Objectives History of Meta-Markup Languages XML Applications: Markup Languages XML Information Modeling Applications XML-Based Architectures XML and Java XML Development Tools Summary Class Project Readings Assignment #1a 3 Part I Introduction 4 2 XML Generics XML means eXtensible Markup Language XML expresses the structure of information (i.e., document content) separately from its presentation XSL style sheets are used to convert documents to a presentation format that can be processed by a target presentation device (e.g., HTML in the case of legacy browsers) Need a
    [Show full text]
  • Wireless Application Protocol WAP
    Wireless Application Protocol WAP F. Ricci 2008/2009 Content Web and mobility Problems of HTML in the mobile context Wap 1.x Motivations Features Architecture Examples of WML (Wireless Markup Language) pages Wap 2.0 XHTML MP Examples Differences with Wap 1.x Examples World Wide Web and mobility Protocol (HTTP, Hypertext Transfer Protocol) and language (HTML, Hypertext Markup Language) of the Web have not been designed for mobile applications and mobile devices, thus creating many problems! Typical transfer sizes HTTP request: 100-350 byte responses avg. <10 kbyte, header 160 byte, GIF 4.1kByte, JPEG 12.8 kbyte, HTML 5.6 kbyte but also many large files that cannot be ignored The Web is not a file system Web pages are not simple files to download static and dynamic content, interaction with servers via forms, content transformation, push technologies etc. many hyperlinks, automatic loading and reloading, redirecting a single click might have big consequences! HTML and mobile devices HTML designed for computers with “high” performance, color high-resolution display, mouse, hard disk typically, web pages optimized for design, not for communication Mobile devices often only small, low-resolution displays, very limited input interfaces (small touch-pads, soft-keyboards) Additional “features” animated GIF, Java AWT, Frames, ActiveX Controls, Shockwave, movie clips, audio, ... many web pages assume true color, multimedia support, high-resolution and many plug-ins Web pages ignore the heterogeneity of end-systems!
    [Show full text]
  • Matml: XML for Information Exchange with Materials Property Data
    MatML: XML for Information Exchange with Materials Property Data Aparna S. Varde1,2 Edwin F. Begley Sally Fahrenholz-Mann 1. Department of Computer Science Computer Integrated Building Electronic Publishing and Content 2. Materials Science Program Processes Group Management Worcester Polytechnic Institute (WPI) National Institute of Standards and ASM International Worcester, MA, USA Technology (NIST) Materials Park, OH, USA [email protected] Gaithersburg, MD, USA sally.fahrenholz- [email protected] [email protected] ABSTRACT 1. INTRODUCTION This paper describes the development and use of MatML, the XML, the eXtensible Markup Language is today a widely Materials Markup Language. MatML is an emerging XML accepted standard for storage and exchange of information. It standard intended primarily for the exchange of materials serves a twofold purpose of providing a data model for storing property information. It provides a medium of communication for information and a medium of communication for exchanging users in materials science and related fields such as manufacturing information over the worldwide web [29]. and aerospace. It sets the stage for the development of semantic Domain-specific markup languages are often defined within the web standards to enhance knowledge discovery in materials context of XML to serve as the means for storing and exchanging science and related areas. MatML has been used in applications information in the respective domains. Some examples of such such as the development of materials digital libraries and analysis markup languages include [14, 9]: of contaminant emissions data. Data mining applications of MatML include statistical process control and failure analysis. • AniML: Analytical Information Markup Language Challenges in promoting MatML involve satisfying a broad range • ChemML: Chemical Markup Language of constituencies in the international engineering and materials science community and also adhering to other related standards in • femML: Finite Element Modeling Markup Language web data exchange.
    [Show full text]
  • Guia Internet Para Periodistas.Pdf
    Indice general Presentación ................................................................................................................................... 9 Introducción ................................................................................................................................. 11 Capítulo 1. Sociedad de la información e Internet. Isabel Fernández Morales ......................... 13 1.1 Sociedad de la información .................................................................................................. 13 1.2 Historia de Internet .............................................................................................................. 15 1.3 Tecnologías de acceso .......................................................................................................... 18 1.4 Tipo de acceso ..................................................................................................................... 18 1.5 Terminales de acceso ........................................................................................................... 20 1.6 Servidores ............................................................................................................................. 20 1.6.1 Servicios de web hosting ............................................................................................... 21 1.7 Proveedores de acceso ......................................................................................................... 22 1.8 Dominios .............................................................................................................................
    [Show full text]
  • Forcepoint DLP Supported File Formats and Size Limits
    Forcepoint DLP Supported File Formats and Size Limits Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 This article provides a list of the file formats that can be analyzed by Forcepoint DLP, file formats from which content and meta data can be extracted, and the file size limits for network, endpoint, and discovery functions. See: ● Supported File Formats ● File Size Limits © 2021 Forcepoint LLC Supported File Formats Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 The following tables lists the file formats supported by Forcepoint DLP. File formats are in alphabetical order by format group. ● Archive For mats, page 3 ● Backup Formats, page 7 ● Business Intelligence (BI) and Analysis Formats, page 8 ● Computer-Aided Design Formats, page 9 ● Cryptography Formats, page 12 ● Database Formats, page 14 ● Desktop publishing formats, page 16 ● eBook/Audio book formats, page 17 ● Executable formats, page 18 ● Font formats, page 20 ● Graphics formats - general, page 21 ● Graphics formats - vector graphics, page 26 ● Library formats, page 29 ● Log formats, page 30 ● Mail formats, page 31 ● Multimedia formats, page 32 ● Object formats, page 37 ● Presentation formats, page 38 ● Project management formats, page 40 ● Spreadsheet formats, page 41 ● Text and markup formats, page 43 ● Word processing formats, page 45 ● Miscellaneous formats, page 53 Supported file formats are added and updated frequently. Key to support tables Symbol Description Y The format is supported N The format is not supported P Partial metadata
    [Show full text]
  • Understanding
    Implementing UBL Mark Crawford UBL Vice Chair XML 2003 9 December 2003 Why Are We Talking About UBL • UBL fulfils the promise of XML for business by defining a standard cross-industry vocabulary • UBL is the ebXML missing link • UBL plus ebXML enables the next generation of eBusiness exchanges – Cheaper, easier, Internet-ready – Extends benefits of EDI to small businesses – Fits existing legal and trade concepts – Allows re-use of data • UBL can provide the XML payload for a wide variety of other web-based business frameworks Overview 1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability 4 Making UBL Happen 5 UBL Phase 2 6 Summary The promise of XML for e-business • Plug ‘n’ play electronic commerce – Spontaneous trade – No custom programming • Ubiquity on the Internet – Dirt-cheap tools – Complete platform independence – Enable true global market availability • Enable universal interoperability – Abandon existing EDI systems – Handle both "publication" document types and "transactional" documents Goals for Successful eBusiness Services • Web-enable existing fax- and paper-based business practices • Allow businesses to upgrade at their own pace • Preserve the existing investment in electronic business exchanges • Integrate small and medium-size businesses into existing electronic data exchange-based supply chains The standardization of XML business documents is the easiest way to accomplish
    [Show full text]
  • Wap, Xhtml and Android
    WAP, XHTML AND ANDROID Jaume Barceló University Carlos III of Madrid Antonio de la Oliva Ruben cuevas Service Engineering Laboratory Ignacio soto BACK IN 1999, • Mobile and Internet communications were separate worlds • Nokia 7110, first mobile phone with a WAP browser. • WAP: Wireless Application Protocol. • Extra-simplified access to the Internet, due to terminal limitations and limited available bandwidth. SMALL LIMITATIONS, • Extremely limited bandwidth • SMS • Circuit-switching • Wait-and-pay • A substantial increase thanks to GPRS (2.5G) ~ 56kbps • Memory and processor limitations • Low resolution monochrome screen • No mouse, 15-keys keyboard WAP PROTOCOL STACK Internet Protocol Stack HTML Wireless Application Environment (WAE) JavaScript 1. Wireless Session Layer (WSP) HTTP 2. Wireless Transaction Protocol (WTP) TLS-SSL 3. Wireless Transport Layer Security (WTLS) 4. Wireless Datagram Protocol (WDP) TCP/IP UDP/IP Bearers: SMS USSD CSD CDMA IS-136 CDPD Etc.. A GW WAS REQUIRED WIRELESS APPLICATION ENVIRONMENT In WAP 1.X Wireless Markup Language (WML) Relies on a card/desk paradigm WMLScript WML EXAMPLE <?xml version="1.0"?> <!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml"> <wml> <card id="card1" title="Tutorial"> <do type="accept" label="Answer"> <go href="#card2"/> </do> <p><select name="name"> <option value="HTML">HTML Tutorial</option> <option value="XML">XML Tutorial</option> <option value="WAP">WAP Tutorial</option> </select></p> </card> <card id="card2" title="Answer"> <p>You
    [Show full text]
  • Abkürzungs-Liste ABKLEX
    Abkürzungs-Liste ABKLEX (Informatik, Telekommunikation) W. Alex 1. Juli 2021 Karlsruhe Copyright W. Alex, Karlsruhe, 1994 – 2018. Die Liste darf unentgeltlich benutzt und weitergegeben werden. The list may be used or copied free of any charge. Original Point of Distribution: http://www.abklex.de/abklex/ An authorized Czechian version is published on: http://www.sochorek.cz/archiv/slovniky/abklex.htm Author’s Email address: [email protected] 2 Kapitel 1 Abkürzungen Gehen wir von 30 Zeichen aus, aus denen Abkürzungen gebildet werden, und nehmen wir eine größte Länge von 5 Zeichen an, so lassen sich 25.137.930 verschiedene Abkür- zungen bilden (Kombinationen mit Wiederholung und Berücksichtigung der Reihenfol- ge). Es folgt eine Auswahl von rund 16000 Abkürzungen aus den Bereichen Informatik und Telekommunikation. Die Abkürzungen werden hier durchgehend groß geschrieben, Akzente, Bindestriche und dergleichen wurden weggelassen. Einige Abkürzungen sind geschützte Namen; diese sind nicht gekennzeichnet. Die Liste beschreibt nur den Ge- brauch, sie legt nicht eine Definition fest. 100GE 100 GBit/s Ethernet 16CIF 16 times Common Intermediate Format (Picture Format) 16QAM 16-state Quadrature Amplitude Modulation 1GFC 1 Gigabaud Fiber Channel (2, 4, 8, 10, 20GFC) 1GL 1st Generation Language (Maschinencode) 1TBS One True Brace Style (C) 1TR6 (ISDN-Protokoll D-Kanal, national) 247 24/7: 24 hours per day, 7 days per week 2D 2-dimensional 2FA Zwei-Faktor-Authentifizierung 2GL 2nd Generation Language (Assembler) 2L8 Too Late (Slang) 2MS Strukturierte
    [Show full text]
  • Preview WML Tutorial (PDF Version)
    1 WML About the Tutorial WML is an XML language used to specify content and user interface for WAP devices like PDA and Mobile Phones. The WAP forum provides a DTD for WML. This tutorial explains how to use WML to develop WAP applications. Audience This tutorial is designed for Software Professionals who are in the need of learning the basics of WML. Prerequisites Before proceeding with this tutorial, you should have a basic understanding of XML, text editor, execution of programs, etc. Disclaimer & Copyright Copyright 2018 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute, or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher. We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness, or completeness of our website or its contents including this tutorial. If you discover any errors on our website or in this tutorial, please notify us at [email protected] i WML Table of Contents About the Tutorial .................................................................................................................................. i Audience ...............................................................................................................................................
    [Show full text]
  • Output Di Stata in Mark-Up Languages: Generazione Automatica Di Tabelle in Html E Latex
    1° CONVEGNO ITALIANO DEGLI UTENTI DI STATA OUTPUT DI STATA IN MARK-UP LANGUAGES: GENERAZIONE AUTOMATICA DI TABELLE IN HTML E LATEX Rosa Gini Jacopo Pasquini Osservatorio di Epidemiologia Agenzia Regionale di Sanità Toscana Roma, 25 Ottobre 2004 OUTPUT DI STATA IN MARK-UP LANGUAGES: Cos’è un linguaggio di tipo MARK-UP? Un linguaggio di markup dei documenti è un insieme di elementi (chiamati "tag") che hanno una o più delle seguenti funzioni: - Descrizione della struttura del documento - Descrizione del contenuto del documento - Controllo di come il documento si presenta all'utente “A way to add computer-understandable information to text files. Certain parts of the text file are interpreted as mark-up instead of content. This markup may contain instructions for the computer. The interpretation of those instructions is defined by the semantics of a particular markup language” (www.watchfire.com) FORMATTAZIONE + CONTENUTI + CONTROLLO TESTO COMPILAZIONE OUTPUT OUTPUT DI STATA IN MARK-UP LANGUAGES: ESEMPI DI LINGUAGGI MARK-UP: -CHTML : (Compact Html– DoCoMotelephones) -CML (Chemical Markup Language) - DocBook (Standard XML - creazione di documentazione) -GML (Geographic Markup Language - sistemi GIS) - HDML (Hendheld Device markup Language - PDA) -HTML (HyperText Markup Language – sviluppo web) - inkML (Ink Markup Language – per input da penne elettroniche) - MathML (mathematical Markup Languages) -MusicXML (Music XML) -RDF (Resource Description Framework –metadata model) -RSS (Really Simple Syndication –web Syndication) - SGML (Standard
    [Show full text]
  • Company Your
    May, 2000 May, TREETIPSTREETIPSTREETIPS • A Publication of Treehouse Software • www.treehouse.com Issue #28 Your MLCompany In a new Partnership with Software AG, Treehouse will bringX Electronic B2B Tools to U.S. Customers Software AG has recently established a U.S. presence and plans to aggressively market Tamino and its full suite of native XML tools for B2B solutions. Therefore, Software AG USA (a wholly-owned subsidiary of Software AG, Darmstadt, Germany) and Treehouse Software, Inc. (TSI) have entered into a distribution partnership whereby TSI will market, sell and support Software AG, Inc.’s native XML e-business products in the United States. TSI will immediately begin selling Tamino, Bolero, and EntireX. "It is our goal to bring our XML technologies to the market through strong partnerships," Dr. Helmut Wilke, President and CEO, Software AG, Inc., said. "We are clearly pleased to partner with Treehouse to help us deliver innovative B2B solutions to our customers." Inside This Issue Partnership with Software AG ............. 1 A Look at Bolero .................................. 4 Editor’s Sproutings/Frontline ............... 2 A Look at EntireX ................................ 5 A Look at Tamino................................. 3 Introduction to XML ............................. 6 Editor’s Sproutings by Joseph Brady Can't Find those Documents? How about using Frontline? There is a new product available from TSI called the Frontline Team Server™ which can help businesses of any size coordinate enterprise-wide information through a Web-based work site that serves as a We have a special offer virtual library. on Frontline for all When the sales representatives from Inmedius, the developers of the product current TSI customers.
    [Show full text]