Localisation/es: Difference between revisions

From FreeCAD Documentation
(Created page with "Compilando el archivo <tt>.ts</tt> de los ejemplos de arriba, se crea un archivo de encabezamiento ''MyMod_de.h''. El mejor sitio para añadirlo es en ''App<Modul>Gui.cpp''. E...")
(Updating to match new version of source page)
(44 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<languages/>
"Localización" es en general el proceso de proveer un software con una interfaz de usuario de con múltiples lenguajes. En FreeCAD puedes cambiar el lenguaje de la interfaz en "Editar→Preferencias→Aplicación". FreeCAD usa [[wikipedia:Qt (toolkit)|Qt]] para facilitar el soporte de múltiples lenguajes. En Unix/Linux, FreeCAD utiliza la configuración local actual de tu sistema como predeterminado.
{{docnav|Branding|Extra python modules}}

<div class="mw-translate-fuzzy">
"Localización" es en general el proceso de proveer un software con una interfaz de usuario con múltiples lenguajes. En FreeCAD puedes cambiar el lenguaje de la interfaz en "Editar→Preferencias→Aplicación". FreeCAD usa [[wikipedia:Qt (toolkit)|Qt]] para facilitar el soporte de múltiples lenguajes. En Unix/Linux, FreeCAD utiliza la configuración local actual de tu sistema como predeterminado.
</div>


== Ayudando a traducir FreeCAD ==
== Ayudando a traducir FreeCAD ==


<div class="mw-translate-fuzzy">
Una de las cosas más importantes que puedes hacer por FreeCAD si no eres un programador es ayudar a traducir el programa a tu idioma. Hacerlo es más fácil que antes, con el uso del sistema de traducción colaborativo en línea [http://crowdin.net Crowdin].
Una de las cosas más importantes que puedes hacer por FreeCAD si no eres un programador es ayudar a traducir el programa a tu idioma. Hacerlo es más fácil que antes, con el uso del sistema de traducción colaborativo en línea [http://crowdin.net Crowdin].
</div>


<div class="mw-translate-fuzzy">
=== Como traducir ===
=== Cómo traducir ===
</div>


<div class="mw-translate-fuzzy">
*Ve a [http://crowdin.net/project/freecad la página del proyecto de traducción de FreeCAD en Crowdin];
*Ve a [http://crowdin.net/project/freecad la página del proyecto de traducción de FreeCAD en Crowdin];
* Ingresa creando un nuevo perfil, o utilizando una cuenta terciaria como tu dirección de Gmail;
* Ingresa creando un nuevo perfil, o utilizando una cuenta terciaria como tu dirección de Gmail;
* Da clic en el lenguaje en que deseas trabajar;
* Da clic en el lenguaje en que deseas trabajar;
* Comienza a traducir al dar clic en el botón de Traducir, al lado de alguno de los archivos. Por ejemplo, ''FreeCAD.ts'' contiene todos los strings para GUI principal de FreeCAD.
* Comienza a traducir al dar clic en el botón de Traducir, al lado de alguno de los archivos. Por ejemplo, ''FreeCAD.ts'' contiene todos los strings para GUI principal de FreeCAD.
* Puedes votar por une traducción existente, o puedes la tuya.
* Puedes votar por une traducción existente, o puedes crear la tuya.
</div>


<div class="mw-translate-fuzzy">
'''Nota''': Si estás participando activamente en la taducción de FreeCAD y quieres ser informado antes de que la nueva versión sea liberada, para que tengas tiempo de revisar tu traducción, porfavor suscríbete a este reporte: http://www.freecadweb.org/tracker/view.php?id=137
'''Nota''': Si estás participando activamente en la taducción de FreeCAD y quieres
ser informado antes de que la nueva versión sea liberada, para que tengas tiempo
de revisar tu traducción, por favor suscríbete a este reporte:
http://www.freecadweb.org/tracker/view.php?id=137
</div>


<div class="mw-translate-fuzzy">
== Traduciendo la wiki ==
</div>


<div class="mw-translate-fuzzy">
=== Traduciendo con Qt-Linguist (la manera antigua) ===
Esta wiki contiene un montón de contenido. El material más importante y actualizado es recopilado en el [[Online_Help_Toc/es|manual]].
</div>


To translate the wiki, you must have wiki edit permissions; see [[FAQ#How can I get edit permission on the wiki?|How can I get edit permission on the wiki?]].
La siguiente información no se debe utilizar y posiblemente se vuelva obsoleta. Se mantiene aquí para que los programadores puedan familiarizarse con su forma de funcionar.


You should also have enough knowledge of wiki markup and follow the general styling guidelines described on [[WikiPages]].
* Abre todos los directorios de lenguaje de FreeCAD que se muestran abajo
* Verifica que un archivo .ts con tu código de lenguaje no existe ("fr" para francés, "de" para alemán, etc...)
* Si existe, puedes descargar el archivo, si quieres modificar/revisar/mejorar la traducción (pulsa en el archivo y descargalo).
* Si no existe, descarga el archivo .ts si código de lenguaje (o cualquier otro .ts disponible, también funcionará)
* Renombra ese archivo con tu código de lenguaje
* Abrelo con el programa Qt-Linguist
* Inicia la traducción (Qt Linguist es muy sencillo de utilizar)
* Una vez esté completamente terminada, guarda tu archivo
* [http://www.freecadweb.org/tracker/main_page.php Envíanos los archivos] así podremos incluirlos en el código fuente de FreeCAD beneficiando también a otros usuarios.


=== Mediawiki Translation Extension===
==== Archivos de traducción disponibles ====


When the wiki moved away from SourceForge, [[User:Yorik|Yorik]] installed [http://www.mediawiki.org/wiki/Help:Extension:Translate MediaWiki's Translation extension] which facilitates translating pages. Advantages of the translation extension are that the page title can now be translated, it keeps track of translations, it notifies if the original page has been updated, and it maintains translations in sync with the original English page.
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Gui/Language/ FreeCAD main GUI]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Complete/Gui/Resources/translations/ Complete Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Drawing/Gui/Resources/translations/ Drawing Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Draft/Languages/ Draft Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/ReverseEngineering/Gui/Resources/translations/ Reverse Engineering Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Fem/Gui/Resources/translations/ FEM Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Robot/Gui/Resources/translations/ Robot Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Image/Gui/Resources/translations/ Image Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Sketcher/Gui/Resources/translations/ Sketcher Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Mesh/Gui/Resources/translations/ Mesh Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Test/Gui/Resources/translations/ Test Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Points/Gui/Resources/translations/ Points Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Raytracing/Gui/Resources/translations/ Raytracing Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Part/Gui/Resources/translations/ Part Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/PartDesign/Gui/Resources/translations/ PartDesign Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/Assembly/Gui/Resources/translations/ Assembly Workbench]
* [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/src/Mod/MeshPart/Gui/Resources/translations/ MeshPart Workbench]


The tool is documented in [http://www.mediawiki.org/wiki/Help:Extension:Translate Help:Extension:Translate], and is part of [http://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle MediaWiki Language Extension Bundle].
== Preparando tus propios módulos/aplicaciones para la traducción ==


To quickly get started on preparing a page for translation, please read the [http://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example Page translation example]. Essentially, a pair of {{incode|<nowiki><translate> ... </translate></nowiki>}} tags need to surround the entire page to activate the translation system, and the page needs to be marked for translation.
=== Prerequisitos ===


To see an example of how the translation tool works, visit the [[Main Page]]. You will see an automatically generated language bar at the top. Click on [[Main Page/de|Hauptseite]] (German), it will get you to [[Main Page/de]]. Right under the title, you can read <small>{{Emphasis|This page is a translated version of the page Main Page and the translation is XX% complete}}</small>, XX being the current percentage of translation. Click on "Translate" at the top of the page to start the translation utility to update, correct and review the existing translation.
Para realizar la localización de tu módulo de aplicación necesitas unas utilidades que vienen con ''Qt''. Puedes descargarlos desde [http://www.trolltech.com/products/qt/downloads Trolltech-Website], pero también están contenidos en [[Third_Party_Libraries/es#LibPack|LibPack]]:
;qmake: Genera los archivos de proyecto
;lupdate: Extrae o actualiza los textos originales en tu proyecto escaneando el código fuente
;Qt-Linguist: 'Qt-Linguist'' es muy sencillo de utilizar y te ayuda en la traducción con buenas características como un libro de frases para las expresiones habituales.


If you go to [[Main Page/de]], you will notice that you cannot edit the page directly anymore by clicking the [Edit] tags, and the top link "Edit" has been substituted by the "Translate" link that opens the translation utility.
=== Setup del proyecto ===


When adding new content, the English page should be created first, then translated into another language. If someone wants to change or add content in a page, the English page should be modified first.
Para iniciar la localización de tu proyecto ve al GUI-Part de tu módulo y escribe en la línea de comandos:
<syntaxhighlight>
qmake -project
</syntaxhighlight>
Esto escanea tu directorio de proyecto buscando archivos que contengan cadenas de texto y crea un archivo de proyecto como el del siguiente ejemplo:
<syntaxhighlight>
######################################################################
# Automatically generated by qmake (1.06c) Do 2. Nov 14:44:21 2006
######################################################################
TEMPLATE = app
DEPENDPATH += .\Icons
INCLUDEPATH += .
# Input
HEADERS += ViewProvider.h Workbench.h
SOURCES += AppMyModGui.cpp \
Command.cpp \
ViewProvider.cpp \
Workbench.cpp
TRANSLATIONS += MyMod_de.ts
</syntaxhighlight>


<div class="mw-translate-fuzzy">
Puedes añadir archivos aquí manualmente. Esta sección <tt>TRANSLATIONS</tt> contiene una lista de los archivos con la traducción para cada idioma. En el ejemplo de arriba ''MyMod_de.ts'' es la traducción al alemán.
Si no estas seguro de como proceder, no dudes en solicitar ayuda en los [http://forum.freecadweb.org/ foros].
</div>


===Important notes===
Ahora necesitas ejecutar <tt>lupdate</tt> para extraer todas las literales de las cadenas de texto en tu interfaz gráfica de usuario. La ejecución de <tt>lupdate</tt> después hacer cambios en el código fuente es siempre segura ya que nunca borra cadenas de texto de tu traducción. Sólo añade nuevas cadenas de texto.


Every wiki user that has "Editor" permissions is able to launch the translate utility and write, save, and review translations.
Ahora necesitas añadir los archivos <tt>.ts</tt> a tu proyecto de VisualStudio. Especifica el siguiente método de construcción personalizado para ellos:
<syntaxhighlight>
python ..\..\..\Tools\qembed.py "$(InputDir)\$(InputName).ts"
"$(InputDir)\$(InputName).h" "$(InputName)"
</syntaxhighlight>
Nota: Introduce el texto en una única línea de comandos, el salto de línea es sólo para propósitos de presentación.


However, only users with "Administrator" permissions are able to mark pages for translation. A page that is not marked for translation won't make use of the translation extension and won't be correctly synchronized to the English information.
Compilando el archivo <tt>.ts</tt> de los ejemplos de arriba, se crea un archivo de encabezamiento ''MyMod_de.h''. El mejor sitio para añadirlo es en ''App<Modul>Gui.cpp''. En nuestro ejemplo esto podría ser ''AppMyModGui.cpp''. Allí añades la línea
<syntaxhighlight>
new Gui::LanguageProducer("Deutsch", <Modul>_de_h_data, <Modul>_de_h_len);
</syntaxhighlight>
to publish your translation in the application.


The left sidebar is also translatable, but only Administrators can modify this element of the site. Please follow the dedicated instructions on [[Localisation Sidebar]].
=== Setting up python files for translation ===


The first time you switch a page to the new translation system, it loses all its old "manual" translations. To recover a translation, you should save an offline copy of the old text before the switch. Then you can use this old translated text to fill in the translation units in the new system. You can also open an earlier version from the history, and get the old text in this way. This has to be done for every language that had a translated page.
To ease localization for the py files you can use the tool "pylupdate4" which accepts one or more py files. With the -ts option you can prepare/update one or more .ts files. For instance to prepare a .ts file for French simply enter into the command line:
<syntaxhighlight>
pylupdate4 *.py -ts YourModule_fr.ts
</syntaxhighlight>
the pylupdate tool will scan your .py files for translate() or tr() functions and create a YourModule_fr.ts file. That file can the be translated with QLinguist and a YourModule_fr.qm file produced from QLinguist or with the command
<syntaxhighlight>
lrelease YourModule_fr.ts
</syntaxhighlight>
Beware that the pylupdate4 tool is not very good at recognizing translate() functions, they need to be formatted very specifically ( see the Draft module files for examples). Inside your file, you can then setup a translator like this (after loading your QApplication but BEFORE creating any qt widget):
<syntaxhighlight>
translator = QtCore.QTranslator()
translator.load("YourModule_"+languages[ln])
QtGui.QApplication.installTranslator(translator)
</syntaxhighlight>
Optionally, you can also create the file XML Draft.qrc with this content:
<syntaxhighlight>
<RCC>
<qresource prefix="/translations" >
<file>Draft_fr.qm</file>
</qresource>
</RCC>
</syntaxhighlight>
and running pyrcc4 Draft.qrc -o qrc_Draft.py creates a big Python containing all resources. BTW this approach also works to put icon files in one resource file


===Old translation instructions===
== Translating the wiki ==


{| class="mw-collapsible mw-collapsed wikitable"
This wiki is hosting a lot of contents, the majority of which build up the manual. You can browse the documentation starting from the [[Main Page]], or have a look at the User's manual [[Online Help Toc]].
|These instructions are for historical background only. Translations should use the new system with the [[#Mediawiki Translation Extension]] described above.
|-
|
So the first step is to '''check if the manual translation has already been started for your language''' (look in the left sidebar, under "manual").<br />
If not, head to the [http://forum.freecadweb.org/ forum] and say that you want to start a new translation, we'll create the basic setup for the language you want to work on.<br />
You must then [[FAQ#How_can_I_get_edit_permission_on_the_wiki.3F|gain wiki edit permission]].<br />
If your language is already listed, see what pages are still missing a translation (they will be listed in red). The technique is simple: '''go into a red page, and copy/paste the contents of the corresponding English page, and start translating'''.<br />
Do not forget to include all the tags and templates from the original English page. Some of those templates will have an equivalent in your language (for example, there is a French Docnav template called Docnav/fr). You should use '''a slash and your language code''' in almost all the links. Look at other already translated pages to see how they did it.<br />
Add a slash and your language code in the categories, like <nowiki>[[Category:Developer Documentation/fr]]</nowiki> <br />
And if you are unsure, head to the forums and ask people to check what you did and tell you if it's right or not.<br />
Four templates are commonly used in manual pages. These 4 templates have localized versions (Template:Docnav/fr, Template:fr, etc...)
* [[Template:GuiCommand]] : is the Gui Command information block in upper-right of command documentation.
* [[Template:Docnav]] : it is the navigation bar at the bottom of the pages, showing previous and next pages.
* [[Template:Userdocnavi]] : gives direct links to the main base pages<br />
''' Page Naming Convention '''<br />
Please take note that, due to limitations in the Sourceforge implementation of the MediaWiki engine, we require that your pages all keep their original English counterpart's name, appending a slash and your language code. For example, the translated page for About FreeCAD should be About Freecad/es for Spanish, About FreeCAD/pl for polish, etc. The reason is simple: so that if translators go away, the wiki's administrators, who do not speak all languages, will know what these pages are for. This will facilitate maintenance and avoid lost pages.<br />
If you want the Docnav template to show linked pages in your language, you can use '''redirect pages'''. They are basically shortcut links to the actual page. Here is an example with the French page for About FreeCAD.<br />
* The page About FreeCAD/fr is the page with content
* The page À propos de FreeCAD contains this code:
#REDIRECT <nowiki>[[About_FreeCAD/fr]]</nowiki>
* In the About FreeCAD/fr page, the Docnav code will look like this:
<nowiki>{{docnav/fr|[[Online_Help_Startpage/fr|Bienvenue dans l'aide en ligne de FreeCAD]]|[[Feature_list/fr|Fonctionnalités]]}}</nowiki>
The page "Bienvenue dans l'aide en ligne de FreeCAD" redirects to Online_Help_Startpage/fr, and the page "Fonctionnalités" redirects to Feature_list/fr.
|}


== Translate the FreeCAD website ==
===Translation plugin===
Translation of the FreeCAD website is now done through [https://crowdin.com/translate/freecad/561/en-en Crowdin]. The file is named {{FileName|homepage.po}}.


== Translate the FreeCAD documentation ==
When the Wiki moved away from SourceForge, [[User:Yorik|Yorik]] installed a [http://www.mediawiki.org/wiki/Help:Extension:Translate Translation plugin] which allows to ease translations between pages. For example, the page title can now be translated. Other advantages of the Translation plugin are that it keeps track of translations, notifies if the original page has been updated, and maintains translations in sync with the original English page.


== Development - How to Add Localisation ==
The tool is documented in [http://www.mediawiki.org/wiki/Help:Extension:Translate Extension:Translate], and is part of a [http://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle Language Extension Bundle].
This section is for developers who want to add localisation to their code.


<div class="mw-translate-fuzzy">
To quickly get started on preparing a page for translation and activating the plugin, please read the [http://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example Page translation example].
== Preparando tus propios módulos/aplicaciones para la traducción ==
</div>


All of the above steps are performed by the "translation scripts" which are run by an administrator periodically.
To see an example of how the Translation tool works once the translation plugin is activated on a page, you can visit the [[Main Page]]. You will see a new language menu bar at the bottom. It is automatically generated. Click for instance on the German link, it will get you to [[Main Page/de]]. Right under the title, you can read "This page is a '''translated version''' of a page Main Page and the translation is xx% complete." (xx being the actual percentage of translation). Click on the "translated version" link to start translation, or to update or correct the existing translation.


Preparing your module for translation is quite easy. First, you need to ensure that you have a "translations" directory in {{FileName|myModule/Gui/Resources}}. Then open a terminal window (or Windows/OSX equivalent) in your "translations" directory and enter the following command:
You will notice that you cannot directly edit a page anymore once it's been marked as a translation. You have to go through the translation utility.
{{Code|code=lupdate -ts myModule.ts}}


This creates an empty translation file. Once this is done, you need to ensure that the translation scripts are updated as in this [https://github.com/FreeCAD/FreeCAD/pull/810 pull request].
When adding new content, the English page should be created first, then translated into another language. If someone wants to change/add content in a page, he should do the English one first.


Everything after this is automatic as far as a developer is concerned. The administrator will extract the text strings, the translators will translate them, then the administrator will extract the translations and update FreeCAD/master.
'''REMARK: The first time you switch a page to the new translation system, it looses all its old 'manual' translations. To recover the translation, you need to open an earlier version from the history, and copy/paste manually the paragraphs to the new translation system.'''


<div class="mw-translate-fuzzy">
Remark: to be able to translate in the wiki, you must of course [[FAQ#How_can_I_get_edit_permission_on_the_wiki.3F|gain wiki edit permission]].
=== Prerequisitos ===
</div>


===Old translation instructions===
=== Older module translation techniques ===
[[Localization Older Methods]] describes the use of translation tools such as Qt Linguist, lupdate, lrelease, pylupdate4, etc in detail. Most of this is no longer required for FreeCAD/master modules, but may be helpful preparing and updating 3rd party modules.
These instructions are for historical background only, while the pages are being passed to the new translation plugin.


== Automating Crowdin Translation Updates ==
So the first step is to '''check if the manual translation has already been started for your language''' (look in the left sidebar, under "manual").
Currently FreeCAD maintainers use the Crowdin API via [[Crowdin Scripts]] to pull and push translations in to Crowdin and back in to the Github repo. The Crowdin API gives FreeCAD maintainers the ability to automate aspects of the project's translation workflow, for more info refer to the [https://support.crowdin.com/api/api-integration-setup/ Crowdin API documentation].


== Related Pages ==
If not, head to the [http://forum.freecadweb.org/ forum] and say that you want to start a new translation, we'll create the basic setup for the language you want to work on.
* [[Crowdin Administration]]
* [[Crowdin Scripts]]


{{docnav/es|Branding/es|Extra python modules/es}}
You must then [[FAQ#How_can_I_get_edit_permission_on_the_wiki.3F|gain wiki edit permission]].


{{Userdocnavi}}
If your language is already listed, see what pages are still missing a translation (they will be listed in red). The technique is simple: '''go into a red page, and copy/paste the contents of the corresponding English page, and start translating'''.


<div class="mw-translate-fuzzy">
Do not forget to include all the tags and templates from the original English page. Some of those templates will have an equivalent in your language (for example, there is a French Docnav template called Docnav/fr). You should use '''a slash and your language code''' in almost all the links. Look at other already translated pages to see how they did it.
[[Category:Developer Documentation/es]]
</div>


[[Category:Wiki]]
Add a slash and your language code in the categories, like <nowiki>[[Category:Developer Documentation/fr]]</nowiki>

And if you are unsure, head to the forums and ask people to check what you did and tell you if it's right or not.

Four templates are commonly used in manual pages. These 4 templates have localized versions (Template:Docnav/fr, Template:fr, etc...)
* [[Template:GuiCommand]] : is the Gui Command information block in upper-right of command documentation.
* [[Template:Docnav]] : it is the navigation bar at the bottom of the pages, showing previous and next pages.

====Page Naming Convention====

Please take note that, due to limitations in the Sourceforge implementation of the MediaWiki engine, we require that your pages all keep their original English counterpart's name, appending a slash and your language code. For example, the translated page for About FreeCAD should be About Freecad/es for Spanish, About FreeCAD/pl for polish, etc. The reason is simple: so that if translators go away, the wiki's administrators, who do not speak all languages, will know what these pages are for. This will facilitate maintenance and avoid lost pages.

If you want the Docnav template to show linked pages in your language, you can use '''redirect pages'''. They are basically shortcut links to the actual page. Here is an example with the French page for About FreeCAD.

* The page About FreeCAD/fr is the page with content
* The page À propos de FreeCAD contains this code:
#REDIRECT <nowiki>[[About FreeCAD/fr]]</nowiki>
* In the About FreeCAD/fr page, the Docnav code will look like this:
<nowiki>{{docnav/fr|Bienvenue sur l'aide en ligne|Fonctionnalités}}</nowiki>
The page "Bienvenue sur l'aide en ligne" redirects to Online Help Startpage/fr, and the page "Fonctionnalités" redirects to Feature list/fr.

If you are unsure how to proceed, don't hesitate to ask for help in the [http://forum.freecadweb.org/ forum].

{{docnav|Branding|Extra python modules}}

[[Category:Developer Documentation]]


{{clear}}
{{clear}}
<languages/>

Revision as of 10:35, 30 March 2019

Branding
Extra python modules

"Localización" es en general el proceso de proveer un software con una interfaz de usuario con múltiples lenguajes. En FreeCAD puedes cambiar el lenguaje de la interfaz en "Editar→Preferencias→Aplicación". FreeCAD usa Qt para facilitar el soporte de múltiples lenguajes. En Unix/Linux, FreeCAD utiliza la configuración local actual de tu sistema como predeterminado.

Ayudando a traducir FreeCAD

Una de las cosas más importantes que puedes hacer por FreeCAD si no eres un programador es ayudar a traducir el programa a tu idioma. Hacerlo es más fácil que antes, con el uso del sistema de traducción colaborativo en línea Crowdin.

Cómo traducir

  • Ve a la página del proyecto de traducción de FreeCAD en Crowdin;
  • Ingresa creando un nuevo perfil, o utilizando una cuenta terciaria como tu dirección de Gmail;
  • Da clic en el lenguaje en que deseas trabajar;
  • Comienza a traducir al dar clic en el botón de Traducir, al lado de alguno de los archivos. Por ejemplo, FreeCAD.ts contiene todos los strings para GUI principal de FreeCAD.
  • Puedes votar por une traducción existente, o puedes crear la tuya.

Nota: Si estás participando activamente en la taducción de FreeCAD y quieres

ser informado antes de que la nueva versión sea liberada, para que tengas tiempo
de revisar tu traducción, por favor suscríbete a este reporte:
http://www.freecadweb.org/tracker/view.php?id=137

Traduciendo la wiki

Esta wiki contiene un montón de contenido. El material más importante y actualizado es recopilado en el manual.

To translate the wiki, you must have wiki edit permissions; see How can I get edit permission on the wiki?.

You should also have enough knowledge of wiki markup and follow the general styling guidelines described on WikiPages.

Mediawiki Translation Extension

When the wiki moved away from SourceForge, Yorik installed MediaWiki's Translation extension which facilitates translating pages. Advantages of the translation extension are that the page title can now be translated, it keeps track of translations, it notifies if the original page has been updated, and it maintains translations in sync with the original English page.

The tool is documented in Help:Extension:Translate, and is part of MediaWiki Language Extension Bundle.

To quickly get started on preparing a page for translation, please read the Page translation example. Essentially, a pair of <translate> ... </translate> tags need to surround the entire page to activate the translation system, and the page needs to be marked for translation.

To see an example of how the translation tool works, visit the Main Page. You will see an automatically generated language bar at the top. Click on Hauptseite (German), it will get you to Main Page/de. Right under the title, you can read This page is a translated version of the page Main Page and the translation is XX% complete, XX being the current percentage of translation. Click on "Translate" at the top of the page to start the translation utility to update, correct and review the existing translation.

If you go to Main Page/de, you will notice that you cannot edit the page directly anymore by clicking the [Edit] tags, and the top link "Edit" has been substituted by the "Translate" link that opens the translation utility.

When adding new content, the English page should be created first, then translated into another language. If someone wants to change or add content in a page, the English page should be modified first.

Si no estas seguro de como proceder, no dudes en solicitar ayuda en los foros.

Important notes

Every wiki user that has "Editor" permissions is able to launch the translate utility and write, save, and review translations.

However, only users with "Administrator" permissions are able to mark pages for translation. A page that is not marked for translation won't make use of the translation extension and won't be correctly synchronized to the English information.

The left sidebar is also translatable, but only Administrators can modify this element of the site. Please follow the dedicated instructions on Localisation Sidebar.

The first time you switch a page to the new translation system, it loses all its old "manual" translations. To recover a translation, you should save an offline copy of the old text before the switch. Then you can use this old translated text to fill in the translation units in the new system. You can also open an earlier version from the history, and get the old text in this way. This has to be done for every language that had a translated page.

Old translation instructions

These instructions are for historical background only. Translations should use the new system with the #Mediawiki Translation Extension described above.

So the first step is to check if the manual translation has already been started for your language (look in the left sidebar, under "manual").
If not, head to the forum and say that you want to start a new translation, we'll create the basic setup for the language you want to work on.
You must then gain wiki edit permission.
If your language is already listed, see what pages are still missing a translation (they will be listed in red). The technique is simple: go into a red page, and copy/paste the contents of the corresponding English page, and start translating.
Do not forget to include all the tags and templates from the original English page. Some of those templates will have an equivalent in your language (for example, there is a French Docnav template called Docnav/fr). You should use a slash and your language code in almost all the links. Look at other already translated pages to see how they did it.
Add a slash and your language code in the categories, like [[Category:Developer Documentation/fr]]
And if you are unsure, head to the forums and ask people to check what you did and tell you if it's right or not.
Four templates are commonly used in manual pages. These 4 templates have localized versions (Template:Docnav/fr, Template:fr, etc...)

  • Template:GuiCommand : is the Gui Command information block in upper-right of command documentation.
  • Template:Docnav : it is the navigation bar at the bottom of the pages, showing previous and next pages.
  • Template:Userdocnavi : gives direct links to the main base pages

Page Naming Convention
Please take note that, due to limitations in the Sourceforge implementation of the MediaWiki engine, we require that your pages all keep their original English counterpart's name, appending a slash and your language code. For example, the translated page for About FreeCAD should be About Freecad/es for Spanish, About FreeCAD/pl for polish, etc. The reason is simple: so that if translators go away, the wiki's administrators, who do not speak all languages, will know what these pages are for. This will facilitate maintenance and avoid lost pages.
If you want the Docnav template to show linked pages in your language, you can use redirect pages. They are basically shortcut links to the actual page. Here is an example with the French page for About FreeCAD.

  • The page About FreeCAD/fr is the page with content
  • The page À propos de FreeCAD contains this code:
#REDIRECT [[About_FreeCAD/fr]]
  • In the About FreeCAD/fr page, the Docnav code will look like this:
{{docnav/fr|[[Online_Help_Startpage/fr|Bienvenue dans l'aide en ligne de FreeCAD]]|[[Feature_list/fr|Fonctionnalités]]}}

The page "Bienvenue dans l'aide en ligne de FreeCAD" redirects to Online_Help_Startpage/fr, and the page "Fonctionnalités" redirects to Feature_list/fr.

Translate the FreeCAD website

Translation of the FreeCAD website is now done through Crowdin. The file is named homepage.po.

Translate the FreeCAD documentation

Development - How to Add Localisation

This section is for developers who want to add localisation to their code.

Preparando tus propios módulos/aplicaciones para la traducción

All of the above steps are performed by the "translation scripts" which are run by an administrator periodically.

Preparing your module for translation is quite easy. First, you need to ensure that you have a "translations" directory in myModule/Gui/Resources. Then open a terminal window (or Windows/OSX equivalent) in your "translations" directory and enter the following command:

lupdate -ts myModule.ts

This creates an empty translation file. Once this is done, you need to ensure that the translation scripts are updated as in this pull request.

Everything after this is automatic as far as a developer is concerned. The administrator will extract the text strings, the translators will translate them, then the administrator will extract the translations and update FreeCAD/master.

Prerequisitos

Older module translation techniques

Localization Older Methods describes the use of translation tools such as Qt Linguist, lupdate, lrelease, pylupdate4, etc in detail. Most of this is no longer required for FreeCAD/master modules, but may be helpful preparing and updating 3rd party modules.

Automating Crowdin Translation Updates

Currently FreeCAD maintainers use the Crowdin API via Crowdin Scripts to pull and push translations in to Crowdin and back in to the Github repo. The Crowdin API gives FreeCAD maintainers the ability to automate aspects of the project's translation workflow, for more info refer to the Crowdin API documentation.

Related Pages

Branding/es
Extra python modules/es