Jump to content

New post: Multi-language field translation export/import (5 Aug 2022)

ryan

By ryan,
in News & Announcements

 Share

Recommended Posts

  • ryan changed the title to New post: Multi-language field translation export/import (5 Aug 2022)
Ivan Gretsky Hero Member

Ivan Gretsky

Posted
Posted

Great new module! Love it! I would also love to extend this module (or have a similar one) to export / import translations for fields' labels / descriptions / notes with per template override support + templates labels. That would make the translation workflow more complete and easy for sites with many languages. @ryan, doesn't your customer accidentally have this need too? ?

  • Like 2
Link to comment
Share on other sites
  • 7 months later...
markus_blue_tomato Sr. Member

markus_blue_tomato

Posted
Posted

Hi @ryan,

after some testing around with our translation management, I saw that we need XLIFF format for most of our translation tools (https://www.across.net/, https://tolgee.io/)

Quote

how to we retain our required "page" and "field" properties in XLIFF

I guess you could take the id attribute in XLIFF and use some [pageid]-[fieldname].

Quote

and how do we provide a value for XLIFF's "file" and "skeleton" fields

Example for file from tolgee export/import file XLIFF:  

<file xmlns="" datatype="plaintext" source-language="de" target-language="de">

And "skeleton" is not mandatory. So there is not need for in in Processwire exports.

Example XLIFF export format for processwire could look like this: 

<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
  <file xmlns="" datatype="plaintext" source-language="en" target-language="de">
    <body>
      <trans-unit id="1234-title" datatype="html">
        <source>Hello World</source>
        <target>Hallo Welt</target>
      </trans-unit>
      <trans-unit id="1234-body" datatype="html">
        <source>
        	<p>
              <strong>A text about flowers.</strong>
            </p>
        </source>
        <target>
        	<p>
              <strong>Ein text über Blumen.</strong>
            </p>
        </target>
      </trans-unit>
    </body>
  </file>
</xliff>

This approach is for XLIFF 1.2 which is used by across and toolge but its depricated.
Maybe it would be good to make an export/import option for XLIFF 1.x and XLIFF 2.x.

More Information about XLIFF in Across: https://www.across.net/en/online-help/sdk/connecting-third-party-systems/crossconnect-for-external-editing/implementation/across-xliff-format?r=1

 

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...