Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translations of UI, table names and values #30

Closed
andreasneumann opened this issue Jan 24, 2013 · 10 comments
Closed

Translations of UI, table names and values #30

andreasneumann opened this issue Jan 24, 2013 · 10 comments

Comments

@andreasneumann
Copy link
Contributor

  • GUI forms and plugin GUI will be translated with QtLinguist
  • table names and value lists will be automatically exported from the main database (through Metadatabase) --> create a .ts file from the database
  • Generate a view for export of the dictionary and the value lists
@ghost ghost assigned 3nids Jan 24, 2013
@m-kuhn
Copy link
Contributor

m-kuhn commented Jan 25, 2013

For the database to .ts converter.

The end result should look like this for german (untested)

<?xml version="1.0" ?>
<!DOCTYPE TS>
<TS version="2.0" language="de" sourcelanguage="en">
<context>
    <name>database</name>
    <message>
        <source>english</source>
        <translation>german</translation>
    </message>
    <message>
        <source>english</source>
        <translation>german</translation>
    </message>
</context>
</TS>

Instead of a database export into another format and subsequent processing to XML (.ts) it might be possible to achieve this file (or a file that needs only a little adjustment) by using postgres xml functions.

3nids added a commit that referenced this issue Mar 5, 2013
@ghost ghost assigned m-kuhn Mar 5, 2013
@3nids
Copy link
Member

3nids commented Mar 5, 2013

The function to list translated elements has been committed.
https://github.com/qgep/QGEP/blob/master/datamodel/translated_elements.sql

@3nids
Copy link
Member

3nids commented Mar 6, 2013

COPY (SELECT * FROM qgep.translated_elements()) TO STDOUT WITH CSV;

3nids added a commit that referenced this issue Mar 6, 2013
@3nids
Copy link
Member

3nids commented Sep 2, 2014

duplicate #46 ?

@m-kuhn
Copy link
Contributor

m-kuhn commented Sep 2, 2014

Possible approaches (taken from #46):

  • Script to translate the project file
  • Have support for project file translation in QGIS core
  • Instead of saving a project file load the project with a plugin

@m-kuhn
Copy link
Contributor

m-kuhn commented Dec 1, 2014

  • Translation of the project file for the demo project
  • In the long run, load the project with a plugin and handle translation there

@m-kuhn
Copy link
Contributor

m-kuhn commented Feb 10, 2015

That's how qwat does form translation: https://github.com/qwat/qWat/tree/master/qwat_dictionary

@m-kuhn m-kuhn added the P2 label Feb 10, 2015
@m-kuhn
Copy link
Contributor

m-kuhn commented Feb 10, 2015

@kfischerar takes care that field names are also translated in the database.
We will then probably generate a .qm translation file from the database.

@3nids
Copy link
Member

3nids commented Feb 13, 2015

@andreasneumann wasn't it you that woud ask Stefan a translation table.

I would expect to get these columns

  • table name
  • field name
  • field name in plain english
  • field name in plain french
  • field name in plain german
  • field comment in plain english
  • field comment in plain french
  • field comment in plain german

Does it make sense?

@m-kuhn
Copy link
Contributor

m-kuhn commented Jun 1, 2015

Database to .ts converter for database term translation.
For further translations, done on transifex https://www.transifex.com/projects/p/QGEP/

@m-kuhn m-kuhn closed this as completed Jun 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants