troca letras

Translating OxS

2011-09-15T01:48:00.000-07:00

Introduction

OJS and OCS are multilingual systems, allowing journals and conferences to publish in a variety of languages. The Public Knowledge Project aims to support English, French, Spanish and Portuguese translations for both OJS and OCS. In addition, translations of both software packages have been completed by the community, and we welcome contributions at any time.

All text you see in a typical fresh OxS interface has been abstracted from the system code, and has in fact been retrieved from one of a number of XML locale files. These files can be found in folders using appropriate ISO locale codes (the Language Code Listing followed by the Country Code Listing), for example en_US for American English, or pt_BR for Brazilian Portuguese. This document will use en_US for its examples.

These locale directories will typically have XML files containing lists of message keys written in them: these message keys and their corresponding values correspond to template lines in the system code itself. The following set of message keys are taken from locale/en_US/locale.xml:

Journal Help
Home
About
User Home
Log In
Register

When the system needs to display a piece of text, it first determines which language should be displayed. The first place it checks is to see which language has been set as the site-wide default by the Site Administrator. If the user is currently looking at a journal, the system instead checks to see which language the Journal Manager has set as the default. And finally, if multiple languages have been installed it checks to see if the user has specified another language to be used instead of the default. More information on administering languages can be found in the section on checking language availability.

Once the system knows which language to display to the user it grabs the message key value from the locale file that belongs to that specific translation: that is, if it needs to display the text relevant to message key="navigation.journalHelp" from the above example, and knows that it should display this in English, it will look in locale/en_US/locale.xml for the appropriate key value, in this case "Journal Help". If the message key doesn't exist (if the locale file is missing that particular key, or doesn't exist on the system in the first place), the system will display the raw message key surrounded by hash marks:

##navigation.journalHelp##
If you ever see that kind of code on an OJS or OCS page, you know that the translation is incomplete. You can take a look at the section on translating to see how to complete it.

Checking Language Availability

You are advised to first check which languages are available from your version of OCS or OJS. If the language you want isn't listed, then check our website for availability.

Warning: We like to ship OJS and OCS with as many finished translations as possible, but we do rely on volunteers for this process, and we don't always have completed translations ready to ship by the time we hit a release date. At times, we opt to ship incomplete translations. Please note that availability in a stock install does not necessarily mean that that particular translation is 100% complete.

Checking Your Software for Available Languages

The first place to check on language availability is from within the software installation itself.

For both OJS and OCS: If you have System Administrator access, log in and go to the System Administrator User Home, and click the Languages link, which will take you to the site-wide languages administration page. This page has two main sections:

Under Language Settings you will find a drop-down box for your Primary Locale: this sets the default language across the entire site; users will be presented with this language by default, until they change their own language preference.

You will also see a list of supported locales, with checkboxes next to them. The selected locales will be available for use by all journals hosted on the site, and will also appear in a language select menu on each site page (which can be overridden on journal-specific pages). If multiple locales are not selected, the language toggle menu will not appear and extended language settings will not be available to journals.
Under Manage Locales you will find a list of installed locales, as well as a list of new locales that haven't been installed.

Beside each installed locale you will see: a link to reload locale, useful if you have made any changes to any locale files; and a link to uninstall locale, which will not remove locale files from your server but will remove them from the list of supported locales.

At the very bottom, beside each locale that hasn't yet been installed, you will see a checkbox. To install a language, check the box next to its name and click Install. The page will reload and the locale will appear under Manage Locales.

If a language is listed as available and installed from the Site Administrator's Languages administration page, you will still have to enable it for your journal or conference for it to be available to users. Log in as a Journal Manager or Conference Manager, and from your User Home click on Languages to visit the journal- or conference-specific language administration page. Here you will be able to set the primary locale for your journal or conference, and likewise enable supported languages to be used journal- or conference-wide. If you enable more than one language, users will be able to toggle between them via a drop-down menu on the sidebar.

Checking the PKP Website for Available Languages

The PKP keeps an up-to-date list of languages and contributors from the relevant project page.

OJS Languages List
OCS Languages List

Information is organized in a table, with the software version along the X axis and the list of languages on the Y axis. Clicking on a language name will take you to an individual language page, which will list the most recent contributors, and any other relevant information.

All languages fall into the following categories:

Complete: either bundled with that particular version of OCS or OJS, or are otherwise available for download from the list.
Needs Updating: these files may be included with the version you are using (the table will indicate this) but incomplete for some reason (they may be a version out of date but still relevant enough to be useful; or they may not have been 100% translated in the first place). If they are listed as not being included with the software version you are using, you can contact the last known maintainers to see if they have any recent files.
If you don't see the language(s) you are looking for listed on either of these lists, please consider undertaking the translation yourself. If you are interested in contributing in such a way, contact us for advice, or consult the rest of this document.

Installing a Language
Language packs are available in tar.gz archive format, and can be installed by following these steps (You will require software such as 7-Zip to decompress the downloaded file):

untar the archive to your OJS or OCS root directory on the server: this will place the translated locale files into the appropriate directories;
add the locale to registry/locales.xml using the following syntax:

(... and so on)

Log into your system as a System Administrator, and go to your Languages page;
Check the checkbox beside the newly-registered locale under Install New Locales and click Install;
After the page reloads, check the checkbox beside the newly-installed locale beside Supported Locales and click Save.
You will then need to either visit each conference or journal you are administering and activate the language from the Journal/Conference Manager Language page. You can do this by checking the box beside Supported Locales and clicking Save.

Warning: Visit your system information page (http:///index.php/index/admin/systemInfo) and review your "registry_dir" variable to be sure you are editing the right locales.xml

Translating OJS and OCS
There are two ways to translate OJS and OCS: you can create a completely manual translation by writing locale files by hand; or you can use the Translator plugin, available in OJS 2.2/OCS 2.1 and above, to finish new translations or edit existing ones.

Creating a Manual Translation

Finding the Files to Translate
To translate OxS into an additional language by hand, first download the latest version of OJS or OCS to a computer (which doesn't have to be a webserver: this can be on your desktop) to extract the files just for translation purposes.

You will require software such as 7-Zip to decompress the downloaded file (e.g., ojs-2.2.3.tar.gz).

Opening the downloaded file with your decompression software will create a directory on your computer based on the downloaded file (e.g., ojs-2.2). Within this directory you will find the following list of subdirectories, where the XML files needing translation are located (en_US is both systems' default language, and by that nature always the most complete; we'll use it as the starting language for a translation):

OxS 2.2 files
locale/en_US: This directory contains the main locale file with the majority of localized OJS text.
dbscripts/xml/data/locale/en_US: This directory contains localized database data, such as email templates.
help/en_US: This directory contains the help files for OJS.
registry/locale/en_US: This directory contains additional localized information such as a country list.
rt/en_US: This directory contains the Reading Tools.
plugins/[plugin category]/[plugin name]/locale, where applicable: These directories contain plugin-specific locale strings.

OxS 2.3+ files
Starting in OJS 2.3, the main locale file in locale/en_US has been split into a number of different locale files; the old email templates file has also been moved from the dbscripts location to the locale/en_US directory; and the files in registry/locale/en_US have also been moved.

locale/en_US: This directory contains a number of locale files, including the emailTemplates.xml locale file. All files should be translated.
lib/pkp/locale/en_US: This directory contains locale files with keys that apply to our entire PKP suite of applications. All files should be translated. It may be that a translator for another application has already translated these files for you; ensure that you check whether these files already exist for the locale you are working on.
help/en_US: This directory contains the help files for OJS.
rt/en_US: This directory contains the Reading Tools.
plugins/[plugin category]/[plugin name]/locale, where applicable: These directories contain plugin-specific locale strings.
[edit] Editing the Files
On opening the XML files, you will notice commonalities between each file: Commented-out topmatter (anything appearing in tags) which you can safely ignore, and then various types of XML tags. There may also be instructions for each locale file, placed in a comments field.

The following XML entity exists in some, but not all of the XML files that you can translate:

This should be change to the language you are translating to, eg. French:

Note: If you notice reference to a specific language in any of the comments fields, feel free to change the reference to your language, although it's not strictly necessary.
Next you will encounter the meat of the locale files, the message keys and their corresponding values. For example, the text that is to be translated in locale/en_US/locale.xml begins like this:

and
between
...

Only the text that sits between the XML tags is in need of translation. Here you can see how that text has been translated into French, after which it has been saved in a file named locale/fr_CA/locale.xml:

et
entre
...

Saving and Properly Placing the Files
Once you have translated the necessary XML files, they will need to be placed in an appropriately named subdirectory, using the ISO locale codes for your language and country (e.g., the files in locale/en_US are translated into French and saved in a subdirectory named locale/fr_CA).

The only critical files that need translation for the system to function properly are found in locale/en_US, dbscripts/xml/data/locale/en_US (versions older than OxS 2.3 only), and registry/locale/en_US (again, only in versions older than OxS 2.3).

New locales must also be added to the file registry/locales.xml, after which they can be installed in the system through the site administration web interface.

Using the Translation Plugin Tool
OJS 2.2 and OCS 2.1 onwards come with a translation plugin that makes the task of updating incomplete translations much easier. You can also start a new translation from scratch, although this takes a bit more work initially.

To enable the plugin, log in as a Journal Manager and go to User Home and then System Plugins; you'll find the Translator plugin listed with the generic plugins. Click on the plugin's Enable link. To access the plugin, return to the System Plugin page, scroll down to the plugin, and click the newly-available Translate link.

You'll now see a list of available (already-installed) locales, and three available actions: Check, Edit and Export.

Checking a Translation
You can check the translation's completeness by clicking the Check link: this will show you a list of missing locale files; keys missing from existing locale files; extra (unneeded) keys; suspicious key lengths (if your translated key value is substantially longer than the English default); and also missing or extra system emails.

If you are missing a locale file, the plugin will allow you to create one and translate the key values from the English default by entering new values against old values into relevant fields. Any other error will display the error message, plus the offending key value in an editable field.

Note: You may be initially surprised by the number of missing locale files: every system plugin requires an individual locale file for its interface, and if you aren't going to be using them you don't have to worry about translating them.

Editing a Translation
If you already know where an error is, you can click the Edit link beside the language name you need to fix, and then click the Edit link next to the specific locale file (please note: clicking the locale filename itself will link you directly to the locale file, which is downloadable).

You will be presented with a list of all keys in that locale file, with their English values alongside your translation values. You can edit your translation values directly here, and save your results, by clicking in the translation value field and making any necessary changes.

If you know the specific key you want to change (say "navigation.journalHelp") enter the key into the search field at the top of the table and press Search: you will be taken to the appropriate page, with the key/value highlighted in yellow.

You can also delete any key from the locale file by clicking the Delete link next to it. Please note, however, that you can't currently add a new key with the Translator plugin: if you do delete a key only to need it later, you will have to add it manually (ie., by editing the file on the server).

Exporting a Translation
You can export a translation by clicking the Export link across from the language name on the Translator plugin page: the system will compress all locale files for that one translation to a downloadable tar.gz package. This is especially useful if you need to migrate a newly-translated language to another OJS or OCS environment, or if you would like to contribute your changes back to the PKP.

Starting a Translation From Scratch
Using the Translation plugin to start a translation from scratch is a little more involved than editing an incomplete, installed translation. You'll need to manually create and upload the main locale file (locales/[your_LANG]/locale.xml) and email templates file (dbscripts/xml/data/locale/[your_LANG]/email_templates_data.xml), and enter your new language into registry/locales.xml, after which your language will appear in the list of editable translations when you visit the Translator plugin. Once this is done you can add new locale files as per the above instructions, and you'll even be able to edit the above two files.

Retrieved from "http://pkp.sfu.ca/wiki/index.php/Translating_OxS"

2009-06-22T19:18:00.000-07:00

VOCÊ SABIA?

Diz-se:
Batatinha quando nasce, esparrama pelo chão…
Enquanto o correto é: Batatinha quando nasce, espalha a rama pelo chão…

No popular se diz: Cor de burro quando foge.
O correto é: Corro de burro quando foge!

Outro que no popular todo mundo erra: Quem tem boca vai à Roma.
O correto é: Quem tem boca vaia Roma.

Outro que todo mundo diz errado: Cuspido e escarrado - quando alguém quer
dizer que é muito parecido com outra pessoa.
Correto é: Esculpido em Carrara (Carrara é um tipo de mármore).

Mais um famoso…
Quem não tem cão, caça com gato…
O correto é: Quem não tem cão, caça como gato… Ou seja, sozinho!

How best to learn the art of subtitling

2009-05-29T09:21:00.001-07:00

Subtitling cannot be learned in the same way that you memorize the words of a foreign language. You have to actually do it.
The various different subtitling rules and regulations are usually conflicting, so the best subtitle is usually the best compromise.
A certain number of basic rules and regulations should be learned when starting out. These may vary for different countries. As the basic principles of subtitling are embedded in these rules, you start understanding the art of subtitling by learning them. Your first automatisms are derived from these basic rules.
Review the material continuously in the initial period, learn just the basic rules and try to avoid learning the other rules, try instead just to understand them. Learning is best done by practicing.

'Doing it right'
Avoid doing things incorrectly and thus picking up incorrect subtitling habits. They're so hard to get rid of! Our courses are designed to encourage you to rehearse the rules each time before you start practicing . The rules will stick in your mind because of the concise phrasing, the words in bold face, the lists and tables and, last but not least, the practical examples in the course.
As too many examples would be distracting and confusing, the number of examples in the course is limited. You will invent your own solutions to problems. The examples in the course serve as illustrations and reminders, and as a reference guide for your ongoing education.
You will find that the collection of pitfalls and bloopers found on this site can be very useful after the initial three month period. They will help you avoid committing the most common errors and improve your translating and subtitling instincts. Dutch subtitlers often use the term 'when the bell rings' in this respect, as an indication that something in a subtitle-to-be is wrong. On closer inspection your instincts usually turn out to have been right and some mistake is found.

Uncertainties
The first uncertainties occur right at the start when you are faced with the daunting task of having to apply many contradicting rules. You tend to hold on to the source language, but by doing so risk producing anglicisms.
In the beginning, you will be preoccupied with your subtitling skills. Primarily with the timing, the in-cues, converting frames into seconds and vice versa. Then, when you start to acquire the skills, your use of the target language will probably be criticized by an editor or mentor. The road from distorted translations that almost all novice subtitlers produce, to rhythmical, easy-to-read, clear and concise subtitles can be a long and hard one.
At a certain point while learning the art of subtitling you will start to see and understand your mistakes. You have a grasp of the principles, but cannot apply them properly yet.. This can be a frustrating period, but it does help you realize where you stand in the course. You will want to keep this necessary and unavoidable 'in between period' as short as possible. Don't try to make it too short however. Keep going over the material.

Automatisms
When first skating on real ice, the cracks in it may drive you crazy. You have to stay sharp all the time, constantly react and consciously adjust your course. But pretty soon your brain takes over! The tension in your muscles disappears, your mind is off the cracks and your fear of falling disappears.
The same kind of auto pilot takes over when you acquire subtitling experience, only this process takes many hours of dedicated practice. Initially, I was surprised to see experienced colleagues producing a lot of subtitles at the end of the day, even though they were tiring. But after six months the same thing happened to me: Automatisms took over whenever possible.
This phenomenon is an extra incentive to avoid picking up bad subtitling habits! You'll pay for them dearly once you start working and relying on automatisms. As mentioned before: the basic rules should become your first automatisms.

Keep having fun...
Many subtitlers want to produce subtitles that are as clear as they can be. They like striving for perfection.
But there is more to it than just the trade. Learning is one of the more satisfying things in life, besides being fun! So keep on exploring. Extend your knowledge. Exchange questions and solutions with colleagues (the Discussion Group provides this possibility). It's nice when a colleague comes up with an unexpected solution for your subtitling problem. Or when a colleague is really happy with the unexpected solution you came up with.

© 2008 Subtitling Worldwide - NL

Tips for movie and documentary producers

2009-05-29T09:12:00.001-07:00

Those interested in producing a movie or documentary or any audio-visual production for television, DVD or cinema, and possessing a certain amount of ambition, would be well advised to take the subject of subtitling into consideration.

It is hard to believe: movie and documentary producers spare no cost or effort to produce a high quality product, but wind up ruining it by overlooking some of the basic principles of subtitling.

A little basic knowledge can prevent spoken dialogue from being excluded from subtitles at the end of a scene, fragments of subtitles disappearing at chapter breaks and, even worse, subtitles appearing across people's faces.

Basic knowledge about subtitling

-subtitles belong at the bottom of the screen,
centered or aligned to the left.
-subtitles should have a minimum duration
of about 1.5 seconds.
-a single line of subtitling, consisting of some 40 characters (including spaces) can be read in 3 seconds.

Do's and Don'ts

-place graphic titles (names of interviewees, information about time of place such as 'Atlanta, August 1956' and 'ten years later' at the very top right or left hand side of the screen, whichever looks best, but never at the bottom.

Why? To prevent subtitles clashing with graphic titles, which looks awful. Subtitles aligned to the right or moved a little to avoid clashing with graphic titles are no solution, as they clutter the screen and may show up on the chin, nose, or even eyes of a talking head. Anybody watching Discovery or National Geographic channels will witness this horrible phenomenon.

-give the subtitle enough time should an important line be spoken just before a scene change or fade-out. Too often subtitlers are forced either to bring in the subtitle too early or leave it too long (into the fade-out or even the next scene), both alternatives to avoid the subtitle disappearing before it's been read properly.

-take chapter breaks into consideration. No subtitles are allowed during the four frames before and after chapter breaks, as this will cause them to disappear on DVD's. A movie maker ignoring this rule ruins his own work. One of the few producers who seem to take this into consideration is Joss Whedon, creator and producer of, for instance, 'Buffy the Vampire Slayers'. In his DVD liner notes he reminds his colleagues not to use dialogue in fade-outs, and his own dialogue is always completed in time.

Por que são importantes as boas legendas

2009-05-29T08:58:00.000-07:00

-As legendas são os textos mais lidos em países
como a Suécia, os Países Baixos e a Bélgica
-As legendas representam apenas 2% dos custos
de produção

-As más legendas arruínam um programa inteiro

-As boas legendas incomodam menos e aumentam
o prazer do espectador

-Nem mesmo os falantes da língua podem passar sempre sem legendas

-Há um número crescente de pessoas com deficiência auditiva que precisam da ajuda das legendas. Assim, até em países onde se dá primazia à dobragem como a Alemanha a legendagem está a assumir um papel cada vez mais importante.

-Basta ver televisão para constatar os danos de uma má legendagem

O que é Legendagem Eletrônica?

2009-05-26T13:14:00.000-07:00

O trabalho de Legendagem Eletrônica inicia-se com a tradução do filme, Longa ou Curta, a partir de um roteiro ou, na falta dele, de um levantamento das falas. A tradução, com ou sem roteiro, é sempre feito com uma cópia do filme, cedida pela produção do evento. Este processo de tradução e posterior adaptação para o formato de legendas, é feito com antecedência à data da Mostra ou Festival.

A legendagem eletrônica é também conhecida como "lançamento de legendas". No momento da projeção do filme, uma pessoa denominada marcador(a) ou lançador(a) controla a exibição das legendas de dentro da sala de cinema ou da sala de projeção em tempo real. O lançador ou marcador de legendas tem à sua frente um computador (conectado a um projetor), onde estão as legendas do filme, e, através de um comando de teclado, projeta ou lança as legendas uma a uma, manualmente e ao vivo, durante o transcorrer do filme.

Para se entender melhor o processo de legendagem eletrônica, é preciso observar que o tempo necessário para a leitura de uma legenda é bem maior que o tempo usado para a fala que corresponde àquele texto. Logo, é impossível traduzir literalmente o que é dito no filme, devendo-se realizar adaptações ou sínteses.

Outra explicação para a necessidade de adaptação na tradução do filme, é que não há como retroceder a leitura para uma tentativa de se entender melhor o que foi dito. Na verdade, trabalha-se com um tipo de texto que requer compreensão imediata.

A boa legenda constitui uma forma de leitura que não desvie a atenção do espectador, senão passará ele a maior parte do tempo tentando entender o que se pretendeu dizer, tirando-lhe o prazer de assistir ao filme.

Um bom tradutor para legendas procura aliar a precisão da informação à adequação do texto ao tempo de leitura, estética e coerência com a fala original.

Entende-se que a legenda não é só a tradução do texto, mas também da imagem, sempre carregada de muita informação. Entretanto, nem sempre temos a possibilidade de aliar imagem e legenda.