DOCSLIB.ORG

Pootle Documentation Release 2.5.1.3

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pootle Documentation Release 2.5.1.3 Pootle Documentation Release 2.5.1.3 Translate.org.za September 16, 2015 Contents 1 All you need to know 3 1.1 User’s guide...............................................3 1.2 Features..................................................5 1.3 Administering a server.......................................... 28 1.4 Developers................................................ 66 1.5 Pootle API................................................ 90 2 Additional Notes 113 2.1 Changelog................................................ 113 2.2 Release Notes.............................................. 115 2.3 External documentation......................................... 129 2.4 License.................................................. 130 i ii Pootle Documentation, Release 2.5.1.3 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.5.1.3 2 Contents CHAPTER 1 All you need to know The following pages cover the documentation of Pootle from a wide variety of perspectives, including user’s, server administrator’s, and developer’s view. 1.1 User’s guide 1.1.1 Getting started Pootle is a web portal that allows you to translate more easily. The name stands for PO-based Online Translation / Localization Engine, but you may need to read this. Pootle is GPL licensed Free Software, and you can download it and run your own copy if you like. You can also help participate in the development in many ways (you don’t have to be able to program). The Pootle project itself is hosted at http://pootle.translatehouse.org where you can find details about source code, mailing lists, etc. Registration While everybody can view the files, only registered users can edit them and receive credit for their effort, so unless your server uses LDAP authentication, the first thing you should do in order to translate, is to register. You can register in the register page (accessible by clicking Register in the menubar) following two simple steps, providing you have a current e-mail address. 1. Fill in your desired user name, a valid e-mail account, and enter your password twice for verification. Then choose Register and an you will receive a message with an activation link in the e-mail address you have provided. 2. When you receive the activation message by e-mail, just click on the activation link and your account will be activated. Login and user settings setup Now that you are a registered user, you can login to Pootle by following the Login link on the top menubar and filling in your credentials. Once you have logged in, your account’s dashboard will be shown, which includes links to your selected languages and projects. 3 Pootle Documentation, Release 2.5.1.3 The first time you log in, no links will be shown since you haven’t chosen any before. You can click on the link provided to change your settings and select your preferred languages and projects. You can set more settings within the same page as well. Browsing the files tree Now that your dashboard is set up, you can reach the desired files for translation directly through the links in it. Another way to find the file you wish to translate is through the main page. The main page displays two categories: languages and projects. Choosing a language will give you the list of projects available for translation into this language; choosing a project will give you the list of languages to which it can be translated. Once you have chosen both the project and the language, you’ll be presented with the files and directories available for translation. Heading to translating If you click on a filename it will start showing all the entries on the file, independently whether the entries are translated or not. This is also known as Translate All. Alternatively, if the translation for a file is not complete, you can click on the summary text (eg, 27 words need attention), which will give you through all the untranslated or fuzzy entries on the file. This mode is also named as Quick Translate. In both cases you’ll be presented with a two-column table, with the strings to be translated on the left, and the current translation on the right. The current edited entry will appear as a text box with the options Skip and Suggest or Submit below it. Naturally you can enter text in the text box and submit it or skip to the next entry. You can also directly access any of the other entries presented by clicking on the numbers on the left-hand side. Other aids from Pootle Pootle’s editor also helps translators by displaying Terminology related to the entry currently being edited. Another helpful feature is the Alternative source language, which displays how the current entry has been translated into other languages. In order for this to work, you must select your desired alternative source languages in you account’s settings. In addition to the above, you can also download the translation file, work offline with your favourite editor and upload the file. For multi-file projects, you can download a ZIP file with all the files for a directory and upload the ZIP file with the translated files. 1.1.2 Administration In default Pootle installations, an admin account (the password matches the username) is created with superuser privileges which can be used to administer the whole site. Note: It’s highly recommended that you change the password for the default admin account on your first login, or even delete the account and assign superuser rights to another user. 4 Chapter 1. All you need to know Pootle Documentation, Release 2.5.1.3 Administration scope Users with administration privileges will have an extra Admin element within the main navigation bar, which gives direct access to the administration functions of the site. Administrators can change the general settings for the site (such as the server title or description), as well as add, edit, and remove users, languages, and translation projects. They are also able to define the default permissions that will apply to the whole site unless otherwise noted. Apart from that, administrators have full rights over all the translation projects, so they can do whatever can be done: translate, suggest, upload new files, update VCS checkouts, ... Adding new site administrators If you want to assign site administration permissions to an already existing user, just go to the Users tab within the Administration page, check the Superuser status checkbox for the user you want to make administrator and click on Save Changes. That’s all! Language administrators Administration rights can be delegated for all tasks within a language. This allows the language administrator to set permissions in the language, set permissions in certain projects in the language, manage files, etc. To appoint a language administrator, visit the language page, and add the administration right on the Permissions tab. 1.2 Features 1.2.1 Backends and storage Authentication Backends LDAP Authentication LDAP configuration can be enabled by appending the ’pootle.core.auth.ldap_backend.LdapBackend’ to the list of AUTHENTICATION_BACKENDS. The settings page lists all the configuration keys available for LDAP. Below a brief example of a working configuration is showcased. The mail addresses are [email protected], the LDAP server is your.ldapserver.org. In this case, we need a specific user account to search in our LDAP server, this user/password is admin/pootle. The LDAP accounts are based on the mail addresses: these are the uids. Finally, John Doe is part of the branch employees on the LDAP. # Authenticate first with an LDAP system and then fall back to Django's # authentication system. AUTHENTICATION_BACKENDS=[ #: Uncomment the following line for enabling LDAP authentication 'pootle.core.auth.ldap_backend.LdapBackend', 'django.contrib.auth.backends.ModelBackend', ] # The LDAP server. Format: protocol://hostname:port AUTH_LDAP_SERVER='ldap://your.ldapserver.org:389' # Anonymous Credentials : if you don't have a super user, don't put cn=... AUTH_LDAP_ANON_DN='cn=admin,dc=website,dc=org' 1.2. Features 5 Pootle Documentation, Release 2.5.1.3 AUTH_LDAP_ANON_PASS='pootle' # Base DN to search AUTH_LDAP_BASE_DN='ou=employees,dc=website,dc=org' # What are we filtering on? %s will be the username (must be in the string) # In this case, we filter on mails, which are the uid. AUTH_LDAP_FILTER='uid= %s' # This is a mapping of Pootle field names to LDAP fields. The key is # Pootle's name, the value should be your LDAP field name. If you don't use the # field or don't want to automatically retrieve these fields from LDAP comment # them out. The only required field is 'dn'. givenName, sn and uid are the names # of the LDAP fields. AUTH_LDAP_FIELDS={ 'dn':'dn', 'first_name':'givenName', 'last_name':'sn', 'email':'uid' } File formats Pootle supports many file formats through the powerful Translate Toolkit API. The Toolkit also provides several format converters for other formats, this will allow you to host a lot of translatable content on Pootle. All these formats can be downloaded for offline use/or translation (for example in Virtaal). We recommend Virtaal for offline translation. They can also be downloaded in XLIFF format. Bilingual formats These formats are translation files that include the source and target language in one file. • Gettext PO • XLIFF New in version 2.0.3. • Qt TS • TBX • TMX Monolingual formats New in version 2.1. These files contain only one language in the file. Pootle supports formats without conversion. • Java properties • Mac OSX strings • PHP arrays • Subtitles in many formats 6 Chapter 1.
Load more

Recommended publications
  • 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]
  • 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]
  • Challenges in Crowd-Sourcing the Positive Side of Things
    Challenges in Crowd-sourcing The positive side of things • 150+ active volunteer translators in over 40 languages • Over 2 million words translated for all Opera products, including browsers, web-sites and -applications • Working both off-line and collaboratively on the web www.opera.com Caveat • Crowd sourcing is not free, nor effortless • Check your applicants • A large crowd is not necessarily a good crowd • Crowd sourcing should only be used for certain tasks • Crowd sourcing should not be used for time critical tasks www.opera.com Protect your assets, teach your crowd • Start small • Put your crowd under embargo/NDA • Appoint at least one contact person per language • Teach your crowd your branding guidelines • Teach your crowd your terminology www.opera.com What we did • Our applications use GNU gettext (PO) • www.opera.com uses XLIFF • Separate content from layout. • Discovered that Open Source is not Open Standards www.opera.com Tools we used • gettext and po4a • Transifex • Translate Toolkit with Pootle and Virtaal • Homebrew applications to bridge the vast gaps www.opera.com Right-to-Left • Semantic markup is key • Proper CSS • Write a separate RTL-stylesheet to negate RTL-challenged CSS • Every time you float:left a kitten dies • Every time you padding:left without a right, another one • Why won’t anyone think of the kittens? • Test in all browsers and on all platforms (1998 anyone) www.opera.com www.opera.com www.opera.com.
    [Show full text]
  • Release 3.2.2 Michalˇcihar
    Weblate Documentation Release 3.2.2 Michal Cihaˇ rˇ Oct 21, 2018 Contents 1 About Weblate 3 1.1 Project goals...............................................3 1.2 Project name...............................................3 1.3 Project website..............................................3 1.4 Authors..................................................3 2 Translators guide 5 2.1 Weblate basics..............................................5 2.2 Registration and user profile.......................................5 2.3 Translating using Weblate........................................ 10 2.4 Downloading and uploading translations................................ 18 2.5 Checks and fixups............................................ 20 3 Application developer guide 29 3.1 Starting with internationalization.................................... 29 3.2 Managing translations.......................................... 34 3.3 Reviewing source strings......................................... 34 3.4 Promoting the translation........................................ 38 3.5 Translation progress reporting...................................... 40 4 Administrators guide 43 4.1 Quick setup guide............................................ 43 4.2 Installation instructions......................................... 46 4.3 Weblate deployments........................................... 70 4.4 Upgrading Weblate............................................ 81 4.5 Backing up and moving Weblate..................................... 84 4.6 Authentication.............................................
    [Show full text]
  • Pootle Documentation Release 2.5.0-Rc1
    Pootle Documentation Release 2.5.0-rc1 Translate.org.za December 01, 2013 Contents i ii Pootle Documentation, Release 2.5.0-rc1 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.5.0-rc1 2 Contents CHAPTER 1 All you need to know The following pages cover the documentation of Pootle from a wide variety of perspectives, including user’s, server administrator’s, and developer’s view. 1.1 User’s guide 1.1.1 Getting started Pootle is a web portal that allows you to translate more easily. The name stands for PO-based Online Translation / Localization Engine, but you may need to read this. Pootle is GPL licensed Free Software, and you can download it and run your own copy if you like. You can also help participate in the development in many ways (you don’t have to be able to program). The Pootle project itself is hosted at http://pootle.translatehouse.org where you can find details about source code, mailing lists, etc. Registration While everybody can view the files, only registered users can edit them and receive credit for their effort, so unless your server uses LDAP authentication, the first thing you should do in order to translate, is to register.
    [Show full text]
  • Weblate-4.0.3
    The Weblate Manual Versión 4.0.3 Michal Čihař 20 de julio de 2020 User docs 1 User docs 1 1.1 Weblate basics .......................................... 1 1.2 Registration and user profile .................................. 1 1.3 Translating using Weblate ................................... 9 1.4 Downloading and uploading translations ........................... 18 1.5 Checks and fixups ........................................ 20 1.6 Searching ............................................. 32 1.7 Application developer guide ................................... 34 1.8 Translation workflows ...................................... 52 1.9 Frequently Asked Questions .................................. 55 1.10 Supported file formats ...................................... 62 1.11 Version control integration ................................... 76 1.12 Weblate’s Web API ....................................... 82 1.13 Weblate Client .......................................... 110 1.14 Weblate’s Python API ...................................... 114 2 Administrator docs 116 2.1 Configuration instructions ................................... 116 2.2 Weblate deployments ...................................... 162 2.3 Upgrading Weblate ....................................... 163 2.4 Backing up and moving Weblate ................................ 169 2.5 Authentication .......................................... 174 2.6 Access control .......................................... 182 2.7 Translation projects ....................................... 188 2.8 Language
    [Show full text]
  • Virtaal Documentation Release 0.7.1
    Virtaal Documentation Release 0.7.1 Translate Jun 26, 2020 Contents 1 Using Virtaal 3 2 Virtaal Features 7 3 Virtaal Screenshots 17 4 Shortcuts 21 5 Tips and Tricks 23 6 Installation 27 7 Contact 29 8 Contributing 31 Index 39 i ii Virtaal Documentation, Release 0.7.1 Virtaal is a graphical translation tool. It is meant to be easy to use and powerful at the same time. Although the initial focus is on software translation (localisation or l10n), we definitely intend it to be useful for several purposes. Virtaal is built on the powerful API of the Translate Toolkit. “Virtaal” is an Afrikaans play on words meaning “For Language”, but also refers to translation. Read more about the features in Virtaal, or view the screenshots. You can also download a screencast (33MB, Ogg Theora format) to see some of these features in action. Learn more about using Virtaal, available shortcuts and some extra tips and tricks for people who want to customise their installation. Contents 1 Virtaal Documentation, Release 0.7.1 2 Contents CHAPTER 1 Using Virtaal Virtaal is meant to be powerful yet simple to use. You can increase your productivity by ensuring you know all the shortcuts and tricks and without being distracted by a cluttered interface. Although most features are available using the mouse, Virtaal is designed to encourage you to work as much as possible with your keyboard to increase your speed and keep the translation fun. When you have no file open in Virtaal, you’ll see the Virtaal dashboard with helpful links to your recent files and various common tasks in the program.
    [Show full text]
  • Release 3.4 Michalˇcihar
    Weblate Documentation Release 3.4 Michal Cihaˇ rˇ Jan 22, 2019 Contents 1 About Weblate 3 1.1 Project goals...............................................3 1.2 Project name...............................................3 1.3 Project website..............................................3 1.4 Authors..................................................3 2 Translators guide 5 2.1 Weblate basics..............................................5 2.2 Registration and user profile.......................................5 2.3 Translating using Weblate........................................ 10 2.4 Downloading and uploading translations................................ 18 2.5 Checks and fixups............................................ 20 3 Application developer guide 29 3.1 Starting with internationalization.................................... 29 3.2 Translation component alerts....................................... 34 3.3 Managing translations.......................................... 35 3.4 Reviewing source strings......................................... 35 3.5 Promoting the translation........................................ 39 3.6 Translation progress reporting...................................... 41 4 Administrators guide 43 4.1 Quick setup guide............................................ 43 4.2 Installation instructions......................................... 46 4.3 Weblate deployments........................................... 72 4.4 Upgrading Weblate............................................ 84 4.5 Backing up and moving Weblate....................................
    [Show full text]
  • Etoys for One Laptop Per Child
    Etoys for One Laptop Per Child Bert Freudenberg, Yoshiki Ohshima, Scott Wallace VPRI Technical Report TR-2009-001 Viewpoints Research Institute, 1209 Grand Central Avenue, Glendale, CA 91201 t: (818) 332-3001 f: (818) 244-9761 Etoys for One Laptop Per Child Bert Freudenberg Yoshiki Ohshima Scott Wallace [email protected] [email protected] [email protected] Viewpoints Research Institute 1209 Grand Central Ave. Glendale, CA 91201 Abstract We present an overview of the “OLPC Etoys” system, describe the intensive two-year development effort that pro- duced the system, and discuss lessons learned. OLPC Etoys is an end-user authoring system for children, which was chosen to be distributed with the OLPC XO laptops at an early stage of the OLPC project. Since we planned to derive OLPC Etoys by evolving an existing, mature system (“Squeakland”), it was expected to be a relatively straightforward undertaking. However, the OLPC XO platform’s special hardware characteristics, the evolution of the Sugar software stack, and the fundamen- tally international and multilingual nature of the project, Figure 1. Etoys Activity’s start up screen. all conspired to make the development effort challenging. Over the two-year course of the project, we successfully recognized educational software package called “Squeak kept up with the challenges, and delivered usable Etoys sys- Etoys” which had been freely available for some years [2] tems for every OLPC release. We steadily improved the UI, [3]. However, VPRI defines itself as a research organiza- added a few high-leverage features, and fixed bugs, with a tion, and since the development work was already “done” small and widely-distributed team and with help from the from a research point of view, VPRI was looking forward to community.
    [Show full text]
  • Open Translation Tools: Disruptive Potential to Broaden Access to Knowledge
    Open Translation Tools: Disruptive Potential to Broaden Access to Knowledge Prepared for Open Society Institute by Allen Gunn Aspiration September 2008 This document is distributed under a Creative Commons Attribution-ShareAlike 3.0 License San Francisco Nonprofit Technology Center, 1370 Mission St., San Francisco, CA 94103 Phone: (415) 839-6456 • [email protected] • Page 1 Table of Contents 1. Executive Summary..........................................................................3 2. Acknowledgments............................................................................6 3. OTT07 Event Background and Agenda...........................................7 4. Translation Concepts......................................................................11 5. Use Cases for Open Content Translation......................................13 6. Open Translation Tools..................................................................17 7. OTT07 “Dream” Translation Tool...................................................22 8. Technical Innovations and Considerations....................................26 9. Related Issues and Gating Factors................................................33 10.Event Outcomes and Ideas for Next Steps....................................36 11.Appendix I: Open Translation Use Cases......................................39 12.Appendix II: Open Translation Tools..............................................49 San Francisco Nonprofit Technology Center, 1370 Mission St., San Francisco, CA 94103 Phone: (415) 839-6456 •
    [Show full text]
  • Translations in Libre Software
    UNIVERSIDAD REY JUAN CARLOS Master´ Universitario en Software Libre Curso Academico´ 2011/2012 Proyecto Fin de Master´ Translations in Libre Software Autor: Laura Arjona Reina Tutor: Dr. Gregorio Robles Agradecimientos A Gregorio Robles y el equipo de Libresoft en la Universidad Rey Juan Carlos, por sus consejos, tutor´ıa y acompanamiento˜ en este trabajo y la enriquecedora experiencia que ha supuesto estudiar este Master.´ A mi familia, por su apoyo y paciencia. Dedicatoria Para mi sobrino Dar´ıo (C) 2012 Laura Arjona Reina. Some rights reserved. This document is distributed under the Creative Commons Attribution-ShareAlike 3.0 license, available in http://creativecommons.org/licenses/by-sa/3.0/ Source files for this document are available at http://gitorious.org/mswl-larjona-docs 4 Contents 1 Introduction 17 1.1 Terminology.................................... 17 1.1.1 Internationalization, localization, translation............... 17 1.1.2 Free, libre, open source software..................... 18 1.1.3 Free culture, freedom definition, creative commons........... 20 1.2 About this document............................... 21 1.2.1 Structure of the document........................ 21 1.2.2 Scope................................... 22 1.2.3 Methodology............................... 22 2 Goals and objectives 23 2.1 Goals....................................... 23 2.2 Objectives..................................... 23 2.2.1 Explain the phases of localization process................ 24 2.2.2 Analyze the benefits and counterparts.................. 24 2.2.3 Provide case studies of libre software projects and tools......... 24 2.2.4 Present personal experiences....................... 24 3 Localization in libre software projects 25 3.1 Localization workflow.............................. 25 3.2 Prepare: Defining objects to be localized..................... 27 3.2.1 Some examples.............................
    [Show full text]
  • Pootle Documentation Release 2.9.0Rc1
    Pootle Documentation Release 2.9.0rc1 Pootle contributors Apr 21, 2018 Contents 1 All you need to know 3 1.1 Features..................................................3 1.2 Installation................................................ 31 1.3 Upgrading................................................ 35 1.4 Administering a server.......................................... 40 1.5 Developers................................................ 91 1.6 Frequently Asked Questions (FAQ)................................... 125 2 Additional Notes 129 2.1 Release Notes.............................................. 129 2.2 License.................................................. 170 i ii Pootle Documentation, Release 2.9.0rc1 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.9.0rc1 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. Aims • Allow Pootle translations to be stored in version control • Abstract diverse version control systems into a standard set of Pootle commands 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 Core concepts Stores and files Pootle contains stores of translation units.
    [Show full text]