DOCSLIB.ORG

Pootle Documentation Release 2.8.2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pootle Documentation Release 2.8.2 Pootle Documentation Release 2.8.2 Pootle contributors Sep 15, 2017 Contents 1 All you need to know 3 1.1 Features..................................................3 1.2 Installation................................................ 33 1.3 Upgrading................................................ 37 1.4 Administering a server.......................................... 41 1.5 Developers................................................ 90 1.6 Frequently Asked Questions (FAQ)................................... 123 2 Additional Notes 125 2.1 Release Notes.............................................. 125 2.2 License.................................................. 164 i ii Pootle Documentation, Release 2.8.2 Pootle is an online tool that makes the process of translating so much simpler. It allows crowd-sourced translations, easy volunteer contribution and gives statistics about the ongoing work. Pootle is built using the powerful API of the Translate Toolkit and the Django framework. If you want to know more about these, you can dive into their own documentation. • Translate Toolkit Documentation • Django Documentation Contents 1 Pootle Documentation, Release 2.8.2 2 Contents CHAPTER 1 All you need to know The following pages cover the documentation of Pootle from a wide variety of perspectives, server administrator’s, and developer’s view. 1.1 Features 1.1.1 Pootle FS Pootle FS Pootle FS is Pootle’s integration with version control plugin systems. It allows Pootle to synchronize with an ex- ternal repository containing your translations, keep them synchronised and manage and resolve any conflicts either automatically or via user input. Warning: Pootle FS is considered beta in Pootle 2.8.0. We’d love you to try it out but please be aware that if you are basing production installs on Pootle FS that you can expect changes that might require manual intervention. Aims • Allow Pootle data to be stored on version control systems • Abstract version control systems into a standard method across all systems • Ensure that we don’t lose any data • Ensure that changes made on Pootle and the filesystem can seamlessly move from one to the other 3 Pootle Documentation, Release 2.8.2 Core concepts Stores and files Pootle contains stores of translation units. The filesystem contains files. Tracked and untracked When a store is associated with a file, it is tracked, if it is not yet associated then it is untracked. And vice versa. States Tracked and untracked files and stores will be in various states depending on a number of things. Have they just appeared, have they changed, have they been removed, etc. Actions Based on the states we can determine what actions might be applicable to the stores and files. Staging We use Pootle FS commands to stage an action. Staging is not execution of those actions but merely preparing these actions for execution. Synchronisation This is the act of executing the staged actions. Understanding operations At any time we are able to query the state of Pootle FS using fs state command. The results of this operation will indicate if there are any actions you need to specify to resolve any conflicts or if there are untracked files. You specify Actions that need to be taken to resolve conflicts or to ensure that files are tracked. This could be adding a file, removing a file or merging conflicting translations. This is the process of staging actions. The final step is to synchronise Pootle and your filesystem. This operation takes your staged actions and executes them. What is a filesystem A filesystem is actually itself a Pootle FS plugin. Currently two exist: 1. localfs - allowing synchronization with the filesystem on which Pootle is running 2. git - synchronization with a Git repository You can write a plugin for any version control system, Pootle FS will ensure that the same commands and operations are used to ensure Pootle and your filesystem stay synchronized. How does Pootle FS relate to update_stores/sync_stores Note: Read this if you have used previous versions of Pootle. Previous versions of Pootle made use of two commands, update_stores and sync_stores, to allow translations to be pushed into Pootle or pulled from Pootle. These two commands still exist but we will be phasing these out in the long term to make everything use Pootle FS. You can find an outline of how to use Pootle FS on your existing Pootle projects in the adding a Pootle FS managed project instructions. Once you are familiar with Pootle FS you can start migrating your projects to Pootle FS. 4 Chapter 1. All you need to know Pootle Documentation, Release 2.8.2 Install Pootle FS plugins for VCS To work with VCS systems Pootle FS requires some additional packages and configuration. Warning: Pootle FS is considered beta in Pootle 2.8.0. We’d love you to try it out but please be aware that if you are basing production installs on Pootle FS that you can expect changes that might require manual intervention. Install the Pootle FS plugins Pootle FS provides support for different VCS systems through plugins, so in order to work with a specific VCS it is necessary to install its plugin. For examples for Git: • Install the plugin: (env) $ pip install --process-dependency-links Pootle[git] • Add the plugin to INSTALLED_APPS: INSTALLED_APPS+=['pootle_fs_git'] This is done once for the whole Pootle server. Next steps Your project is now ready to use Pootle FS with the chosen VCS systems, you can now proceed to add a Pootle FS managed project. Add a Pootle FS managed project Pootle FS can work with different VCS systems as well as with the local file system. The following steps outline the setup of a Pootle FS based project: Install Pootle FS plugins Note: Pootle FS will work out of the box when synchronizing with the local file system. If this is the case you can safely skip this step. Synchronizing against any version control system requires you add some additional packages and configuration. Create a project to be managed by Pootle FS Create a project as usual, setting the Project Tree Style to Allow Pootle FS to manage filesystems. 1.1. Features 5 Pootle Documentation, Release 2.8.2 Provide Pootle FS configuration for the project Once the project is created you need to configure Pootle FS. You can accomplish this with the command line or the web UI. The UI is by far the simplest way and is outlined here: • Click on the Filesystems link below the project edit form in the project admin UI. • Add the Backend configuration: – Set the Filesystem backend to localfs as we are working against files stored on the local filesystem. – Set the Backend URL or path to point to the translation files on Pootle’s local filesystem, e.g. /path/ to/translations/MYPROJECT/ – Set the Translation path mapping for your project, for example /<language_code>/ <dir_path>/<filename>.<ext> Note: If you are setting up Pootle FS for a VCS then configure as follows: – Set the Filesystem backend to the required VCS backend. – Set the Backend URL or path to point to the repository, e.g. [email protected]:user/repo.git 6 Chapter 1. All you need to know Pootle Documentation, Release 2.8.2 • If not all of your project’s language codes match those available in Pootle, then add language mapping configu- rations for those languages. For example match fr_FR on your filesystem to fr on Pootle. Connect Pootle FS with VCS repository Note: You can safely skip this step if you are setting up the project to synchronize with the local file system. • Create a SSH key: $ sudo -u USER-RUNNING-POOTLE ssh-keygen -b 4096 • Tell your upstream repo about the public key, allowing Pootle to be able to push to the repo. – In GitHub: * Either use the public key as a Deploy key for the repository on GitHub, * Or (preferred) add the public key to a GitHub user’s SSH and GPG Keys. In most cases you want to create a specific Pootle GitHub user. Pull the translations into Pootle Once the project is created and properly set up we can pull the translations into Pootle: (env) $ pootle fs state MYPROJECT (env) $ pootle fs add MYPROJECT (env) $ pootle fs sync MYPROJECT Next steps Your project is now ready to use Pootle FS. In order to keep Pootle and the filesystem or VCS synchronised you will need to learn how to use Pootle FS. Migrating to Pootle FS While Pootle will continue to support update_stores and sync_stores this will eventually be deprecated. Thus it makes sense to migrate your projects to Pootle FS. These steps will convert a project currently hosted in POOTLE_TRANSLATION_DIRECTORY into a Pootle FS localfs project. Preparation 1. (optional) Disable the project to prevent translators working on the stores. You can also, quite safely, perform the migration live. 2. Run sync_stores to ensure that all translations in Pootle are on the filesystem. The filesystem and Pootle should now have exactly the same data. (env) $ pootle sync_stores --project=MYPROJECT 1.1. Features 7 Pootle Documentation, Release 2.8.2 Setup Pootle FS 1. In the Project Admin interface, change the Project Tree Style to Allow Pootle FS to manage filesystems. 2. Click on the Filesystems link below the project edit form and set the following: • Filesystem backend to localfs • Backend URL or path to the value of POOTLE_TRANSLATION_DIRECTORY + MYPROJECT, e.g. /path/to/pootle/translations/MYPROJECT • Translation path mapping to the one your project uses, or pick one of the existing Translation mapping presets. First synchronization Now that our project is setup we can initiate the first synchronization to ensure all files are tracked: (env) $ pootle fs add --force MYPROJECT (env) $ pootle fs sync MYPROJECT This will use translations from Pootle and ignore those on the filesystem. 8 Chapter 1. All you need to know Pootle Documentation, Release 2.8.2 Variations on the theme The process above outlines how you can move an update_stores project to Pootle FS on the local filesystem with Pootle winning.
Load more

Recommended publications
  • Workflow Manual
    Published on Multilingual Online Translation (http://www.molto-project.eu) D3.3 Translation Tools – Workflow Manual Contract No.: FP7-ICT-247914 Project full title: MOLTO - Multilingual Online Translation Deliverable: D3.3 MOLTO translation tools – workflow manual Security (distribution level): Public Contractual date of delivery: M31 Actual date of delivery: April 2013 Type: Manual Status & version: Final Author(s): Inari Listenmaa, Jussi Rautio Task responsible: UHEL Other contributors: Lauri Alanko, John Camilleri, Thomas Hallgren Abstract Deliverable D3.3 consists of a manual and a description of the workflow of the MOLTO translation tools. The document introduces the components: the open-source translation management system Pootle, the Simple Translation Tool, which supports many different translation methods and the Syntax Editor, which allows to modify text by manipulating abstract syntax trees. The document presents two translation workflows. The first scenario integrates MOLTO tools in a professional translation on fixed source, using Pootle. MOLTO translations with GF grammars are added in machine translation options. Another direction taken is the population of translation memory with GF generated data. In the second workflow, the translator is authorized to do changes to source. The tools used in this scenario are the Simple Translation Tool and the Syntax Editor. 1. Introduction This Deliverable D3.3, is a manual and a description of workflow for the translation tools produced within WP3. As stated in the previous Deliverables 3.2 and 3.1, the user of the translation tools is not required to know how to write GF grammars. They are either translators, whose job is to translate from fixed source, or they are authorized to modify the source text in order to fit into the structures covered by the domain-specific grammar(s).
    [Show full text]
  • Structuring Your Content & Projects for Continuous Localization
    GUIDE Structuring Your Content & Projects for Continuous Localization Table of Contents Introduction: Lessons from 10+ Years of Taking Companies Global • Learning Challenges to Overcome Them • A Guide for Fast, Tech-Focused Companies • What Not to Do: Common Software Localization Mistakes Part 1: Internationalization • The Importance of Internationalization • Finding & Fixing Internationalization Bugs • The Software Architecture Checklist Part 2: Structuring Your Files • Organizing Your Projects & Resources • Building a Global Content Repository • Structuring Your Files • Common Localization File Formats Part 3: Workflows & Integrations • Finding the Best Approach for Your Team • How to Integrate with Your TMS Wrap-Up • The Future of Localization: Continuous & Cloud-Based • About Transifex Native Transifex | Structuring Your Content & Projects for Continuous Localization 2 Introduction Lessons from 10+ Years of Taking Companies Global A Guide for Fast, Tech-Focused Companies We put together this guide for fast-moving companies like you — to empower your team to understand and leverage the power of continuous localization to overcome all those challenges that come with the outdated form of localization (a lot of manual files and email chains). In this guide, we break down the ins and outs of effectively structuring your content and projects for continuous localization, so you can finally localize at the speed of your content and product creation. Learning Challenges to Overcome Them In our journey building this platform, we’ve learned firsthand
    [Show full text]
  • Webinar: Translation Memory and Machine Translation
    Legal Services National Technology Assistance Project www.lsntap.org Webinar: Translation Memory and Machine Translation Jillian Theil, Claudia Johnson, Diana Glick, Leland Sampson, Maria Mindlin and Sart Rowe Machine Translation The Perils of Google Translate Typically Google translate tool will give you broken language translations. You might be able to tell what the translation is saying but it will be grammatically incorrect and use wrong words. The key when creating something like a sign, is to use more visuals and less words. Arrow signs, people icons, Dollar signs etc. Check for existing resources - look for signs that already exist and you can see what they are doing. Consider using visuals for wayfinding - arrows, etc Conduct Plain language review and editing Ensure your signage is readable (font etc) Back translation is running a translation back into english to ensure it is correct. Case Study: Using chinese as an example: the word for computer mouse is a different word than the animal mouse - so google translate will translate a sentence about this wrong. If possible obtain a legal review of the translation from an attorney / translator. Is it Ever OK to use Google Translate? It’s ok for informal communications, for general understanding or when you are in a complete bind and have no other options. Translation Workflow for Lingotek and People’s Law Library 1. Volunteer contacts them, and they qualify that volunteer 2. The volunteer selects an article to translate and that article is uploaded to lingotek 3. The volunteer performs the actual translation and then the article is assigned to a volunteer reviewer who is a licensed attorney 4.
    [Show full text]
  • Introducing a Cat Tool to Translate: Wordfast
    Indonesian Journal of English Language Studies Vol. 2, Number 1, February 2016 Introducing a Cat Tool to Translate: Wordfast Fika Apriliana, Ardiyarso Kurniawan, Sandy Ferianda, and Fidelis Chosa Kastuhandani ABSTRACT This article aims at introducing CAT tools to those prospective translators who are familiar with with the tools for the first time. Some of the CAT tools must be paid for while some others are free. This article is to inform the readers about the list of free and paid CAT tools, advantages and disadvantages of those tools. One does not need special training for using a free CAT tool while using the paid CAT tools, one needs some special preparation. This article is going to focus more on Wordfast Pro as the second most widely used CAT tools after SDLTrados. Wordfast Pro is a paid software the functioning of which is based on the creation of a Translation Memory which facilitates and speeds up the translator's work. This article is going to briefly explain the advantages of Wordfast Pro and the steps of using it. The translation example is presented to reveal the different translation results of Wordfast Pro as a paid CAT tool and OmegaT as a free CAT tool. Therefore, the article will facilitate those who intend to know more about Wordfast Pro and start using it. Keywords: CAT tools, Wordfast Pro, OmegaT INTRODUCTION When using CAT tools, it is Computerized translation has attracted immediately clear which parts of the text the attention of a large number of people must be translated; the unchanging who work directly or indirectly on portions are transferred accurately and translational issues such as professional directly; the time savings due to repeating translators, teachers, linguists, researchers expressions is huge; and expressions are and future translators.
    [Show full text]
  • Teaching Video Game Translation: First Steps, Systems and Hands-On Experience Ensinando Tradução De Videogame: Primeiros Passos, Sistemas E Experiência Prática
    http://periodicos.letras.ufmg.br/index.php/textolivre Belo Horizonte, v. 11, n. 1, p. 103-120, jan.-abr. 2018 – ISSN 1983-3652 DOI: 10.17851/1983-3652.11.1.103-120 TEACHING VIDEO GAME TRANSLATION: FIRST STEPS, SYSTEMS AND HANDS-ON EXPERIENCE ENSINANDO TRADUÇÃO DE VIDEOGAME: PRIMEIROS PASSOS, SISTEMAS E EXPERIÊNCIA PRÁTICA Marileide Dias Esqueda Universidade Federal de Uberlândia [email protected] Érika Nogueira de Andrade Stupiello Universidade Estadual Paulista “Júlio de Mesquista Filho” [email protected] ABSTRACT: Despite the significant growth of the game localization industry in the past years, translation undergraduate curricula in Brazil still lacks formal training in game localization, often leaving novice translators no alternative but to search for the required skills informally in game translation communities. Designing a video game localization course in translation undergraduate programs in public universities is a complex task in today’s reality, particularly due to limited access to free and authentic materials. This paper describes a game localization teaching experience at the undergraduate level with special focus on how to handle the linguistic assets of the online race game SuperTuxKart, while trying to shed some light on potential translation requirements of entertainment software and its incorporation into translation programs. KEYWORDS: video game localization; video game translation; translator training; translation undergraduate program; SuperTuxKart. RESUMO: A despeito do significativo crescimento da indústria de localização de games nos últimos anos, os currículos dos cursos de graduação em tradução ainda carecem de formação específica na localização de games, geralmente não oferecendo ao tradutor em formação alternativas outras senão a de adquirir informalmente, ou em comunidades on- line de gamers, os conhecimentos sobre a tradução desse tipo de material.
    [Show full text]
  • An Empirical Study on the Influence of Translation Suggestions’ Provenance Metadata
    An empirical study on the influence of translation suggestions’ provenance metadata A Thesis Submitted for the Degree of Doctor of Philosophy by Lucía Morado Vázquez Department of Computer Science and Information Systems, University of Limerick Supervisor: Dr Chris Exton Co-Supervisor: Reinhard Schäler Submitted to the University of Limerick, August 2012 i Abstract In the area of localisation there is a constant pressure to automate processes in order to reduce the cost and time associated with the ever growing workload. One of the main approaches to achieve this objective is to reuse previously-localised data and metadata using standardised translation memory formats –such as the LISA Translation Memory eXchange (TMX) format or the OASIS XML Localisation Interchange File Format (XLIFF). This research aims to study the effectiveness and importance of the localisation metadata associated with the translation suggestions provided by Computer-Assisted Translation (CAT) tools. Firstly, we analysed the way in which localisation data and metadata can be represented in the current specification of XLIFF (1.2). Secondly, we designed a new format called the Localisation Memory Container (LMC) to organise previously-localised XLIFF files in a single container. Finally, we developed a prototype (XLIFF Phoenix) to leverage the data and metadata from the LMC into untranslated XLIFF files in order to improve the task of the translator by helping CAT tools, not only to produce more translation suggestions easily, but also to enrich those suggestions with relevant metadata. In order to test whether this “CAT-oriented” enriched metadata has any influence in the behaviour of the translator involved in the localisation process, we designed an experimental translation task with translators using a modified CAT tool (Swordfish II).
    [Show full text]
  • Translate's Localization Guide
    Translate’s Localization Guide Release 0.9.0 Translate Jun 26, 2020 Contents 1 Localisation Guide 1 2 Glossary 191 3 Language Information 195 i ii CHAPTER 1 Localisation Guide The general aim of this document is not to replace other well written works but to draw them together. So for instance the section on projects contains information that should help you get started and point you to the documents that are often hard to find. The section of translation should provide a general enough overview of common mistakes and pitfalls. We have found the localisation community very fragmented and hope that through this document we can bring people together and unify information that is out there but in many many different places. The one section that we feel is unique is the guide to developers – they make assumptions about localisation without fully understanding the implications, we complain but honestly there is not one place that can help give a developer and overview of what is needed from them, we hope that the developer section goes a long way to solving that issue. 1.1 Purpose The purpose of this document is to provide one reference for localisers. You will find lots of information on localising and packaging on the web but not a single resource that can guide you. Most of the information is also domain specific ie it addresses KDE, Mozilla, etc. We hope that this is more general. This document also goes beyond the technical aspects of localisation which seems to be the domain of other lo- calisation documents.
    [Show full text]
  • Open-Source Tools - Freie Translationstechnologie Für Übersetzer
    Peter Sandrini Universität Innsbruck Open-Source Tools - Freie Translationstechnologie für Übersetzer Mit freier Software kostenlos zum Erfolg 27.9.2014 Überblick I. Was ist freie Software? II. Freie Translationstechnologie III.Freie Translationstechnologie im Set USBTrans und tuxtrans IV.Arbeitsabläufe eines Übersetzers ✔ Übersetzen eines Word-Dokumentes mit TM-Support ✔ Übersetzen einer Website mit TM-Support ✔ Maschinenübersetzung nutzen ✔ Erstellen eines TM anhand vorhandener Übersetzungen ✔ Qualitätsprüfung ✔ Verwalten eigener Terminologiesammlungen ✔ Terminologieextraktion ✔ Referenzkorpus erstellen ✔ Dateiformate konvertieren ... 27.9.2014 Mit Technologie kostenlos zum Erfolg 2 frei ? Open-Source? Freiheit zum – benutzen Lizenzen: – anpassen ● GNU GPL ● – weitergeben Apache License 2.0 ● BSD 2/3 – verbessern ● (L)PGL ● MIT license ● Mozilla Public License 2.0 ● Eclipse Public License ● Creative Commons 27.9.2014 Mit Technologie kostenlos zum Erfolg 3 27.9.2014 Mit Technologie kostenlos zum Erfolg 4 Warum eigentlich? ● Kostenschonenden Karrierebeginn ermöglichen ● erleichterte Kooperation ● Vermeiden von Urheberrechtsverletzungen durch Softwarepiraterie ● volle Kontrolle über eigenen PC ● Einfaches Handling ohne Lizenz oder Aktivierungscode ● Beteiligung an Entwicklercommunities ● macht aus (abhängigen) Konsumenten (eigenverantwortliche) Akteure 27.9.2014 Mit Technologie kostenlos zum Erfolg 5 TEnTs ● Translation Environment Tools (TenT) umfassende Applikation für Übersetzer mit allen nötigen Hilfsmitteln ● Oberbegriff für „Translation-Memory-
    [Show full text]
  • Lingo Translation Guide
    USER GUIDE MADCAP LINGO 11 Translation Copyright 2019 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software described in this document is fur- nished under a license agreement or nondisclosure agreement. The software may be used or copied only in accord- ance with the terms of those agreements. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or any means electronic or mechanical, including photocopying and recording for any pur- pose other than the purchaser's personal use without the written permission of MadCap Software. MadCap Software 9191 Towne Center Drive, Suite 150 San Diego, California 92122 858-320-0387 www.madcapsoftware.com THIS PDF WAS CREATED USING MADCAP FLARE. CONTENTS CHAPTER 1 Introduction 6 Types of Content 7 Steps for Translating Files 9 CHAPTER 2 Translation Features 13 Filter 14 Translation Memory 25 Machine Translation 26 Termbases 26 Notes for Segments 27 Adding Numbers from Source Segments 31 Right-Click/Keyboard Shortcut Options 32 Live Preview Mode 34 Inline Formatting and Tags 43 Setting the Translated Status of Files 51 Sending Translated Content for Review 53 CHAPTER 3 Translation Memory 56 Translation Memory Features 58 CONTENTS iii Steps for Using Translation Memory 67 Creating a Translation Memory Database 69 Adding a Translation Memory Database 72 Choosing a Translation Memory Database 73 Statuses and Matches 83 Applying Translation Memory Suggestions 94 Editing a Translation Memory Database
    [Show full text]
  • Beyond Translation Memory: Computers and the Professional Translator Ignacio Garcia, University of Western Sydney
    The Journal of Specialised Translation Issue 12 – July 2009 Beyond Translation Memory: Computers and the Professional Translator Ignacio Garcia, University of Western Sydney ABSTRACT Translation has historically been performed by bilinguals equipped with specialised topic knowledge. In the mid 20 th century, textual theory and discourse analysis saw emphasis on a top-down, whole-text approach that paved the way for modern professional translators as linguistic transfer experts. This professionalisation was further driven by the digital revolution in the 90s which caused a huge increase in translation demand, and the creation of purpose-designed translation tools—principally translation memory (TM). However, the same technological processes that briefly empowered the professional translator also signalled a return to a bottom-up approach by concentrating on the segment. Twenty years on, translation tools and workflows continue to narrow this focus, even tending towards simple post-editing of machine translated output. As a result, topic-proficient bilinguals are again entering mainstream translation tasks via simplified translation management processes and crowdsourcing approaches. This article explores these recent trends and predicts that, over the next decade, professional translators will find it increasingly difficult to survive as linguistic transfer experts alone. KEYWORDS Translation, localisation, localization, translation memory, machine translation, professional translation, translation as a utility, hive translation. Introduction The digital age has affected all professions, but change has been felt by translators more keenly than most. Like the rest of the ‘knowledge sector,’ translators are obliged to work on computer screens and do their research using the web. Unlike their colleagues however, they have been propagating this new work environment and fomenting change precisely by their role in translating it.
    [Show full text]
  • Enhancing Open-Source Localization
    San Jose State University SJSU ScholarWorks Master's Projects Master's Theses and Graduate Research 2010 Enhancing open-source localization Farzana Forhad San Jose State University Follow this and additional works at: https://scholarworks.sjsu.edu/etd_projects Part of the Computer Sciences Commons Recommended Citation Forhad, Farzana, "Enhancing open-source localization" (2010). Master's Projects. 57. DOI: https://doi.org/10.31979/etd.5kf8-9ykm https://scholarworks.sjsu.edu/etd_projects/57 This Master's Project is brought to you for free and open access by the Master's Theses and Graduate Research at SJSU ScholarWorks. It has been accepted for inclusion in Master's Projects by an authorized administrator of SJSU ScholarWorks. For more information, please contact [email protected]. Enhancing open-source localization CS298 Report Enhancing open-source localization A Writing Project Presented to The Faculty of computer Science San Jose State University In Partial Fulfillment of the Requirement for the Degree Master of Science By Farzana Forhad May 2010 - 1 - Enhancing open-source localization CS298 Report © 2010 Farzana Forhad - 2 - Enhancing open-source localization CS298 Report APPROVED FOR THE DEPARTMENT OF COMPUTER SCIENCE Dr. Chris Pollett Dr. Robert Chun Frank Butt - 3 - Enhancing open-source localization CS298 Report ABSTRACT Pootle is a web portal which is designed to be a web translation tool. We can run Pootle like an internet server and run a local copy on an intranet. Pootle has a user friendly interface which ensures better quality and easier translation of projects. Users can log into the Pootle and create their own projects under any language, and they can also add or retrieve any language from any project or any project from any language.
    [Show full text]
  • Translate Toolkit Documentation Release 2.0.0
    Translate Toolkit Documentation Release 2.0.0 Translate.org.za Sep 01, 2017 Contents 1 User’s Guide 3 1.1 Features..................................................3 1.2 Installation................................................4 1.3 Converters................................................6 1.4 Tools................................................... 57 1.5 Scripts.................................................. 96 1.6 Use Cases................................................. 107 1.7 Translation Related File Formats..................................... 124 2 Developer’s Guide 155 2.1 Translate Styleguide........................................... 155 2.2 Documentation.............................................. 162 2.3 Building................................................. 165 2.4 Testing.................................................. 166 2.5 Command Line Functional Testing................................... 168 2.6 Contributing............................................... 170 2.7 Translate Toolkit Developers Guide................................... 172 2.8 Making a Translate Toolkit Release................................... 176 2.9 Deprecation of Features......................................... 181 3 Additional Notes 183 3.1 Release Notes.............................................. 183 3.2 Changelog................................................ 246 3.3 History of the Translate Toolkit..................................... 254 3.4 License.................................................. 256 4 API Reference 257 4.1
    [Show full text]