-
Notifications
You must be signed in to change notification settings - Fork 28
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
Comments
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. |
The function to list translated elements has been committed. |
COPY (SELECT * FROM qgep.translated_elements()) TO STDOUT WITH CSV; |
duplicate #46 ? |
Possible approaches (taken from #46):
|
|
That's how qwat does form translation: https://github.com/qwat/qWat/tree/master/qwat_dictionary |
@kfischerar takes care that field names are also translated in the database. |
@andreasneumann wasn't it you that woud ask Stefan a translation table. I would expect to get these columns
Does it make sense? |
Database to .ts converter for database term translation. |
The text was updated successfully, but these errors were encountered: