Re: [asciidoc-wg] Localization of AsciiDoc content

[Steven Anderson <sanderson@xxxxxxxxxxxx>]

Our vendor uses a custom, in-house, plugin for SDL Studio to help them with localization and translation.    

Basically the purpose of the plugin is to parse the files so that the structure is preserved rather than being pulled into the translation environment and potentially broken.  Inline formatting elements are pulled in but tagged so that the translator can move them around the text but not break them (bold text in the middle of sentences for example).

Interestingly, SDL Studio already has functionality for MarkDown, but our vendor doesn't use that, they have created their own plugin for it as well.  

     Steve Anderson

      sanderson@xxxxxxxxxxx

On Mon, Feb 22, 2021 at 12:10 AM Robert Kratky <rkratky@xxxxxxxxxx> wrote:

Hi,

As Red Hat has transitioned to AsciiDoc for most of its docs, we're faced with questions regarding content translation. With DocBook, the tight structure and semanticity made it straightforward for our l10n teams.

However, our l10n tooling is not ready for AsciiDoc. I'd like to ask whether there are other organizations dealing with this. Specifically:

English AsciiDoc -> Translated AsciiDoc -> Translated output (HTML, or whatever)

(As opposed to translating the HTML output.)

Thanks.

Regards,

--
Robert Kratky
Content Strategist
Red Hat

_______________________________________________
asciidoc-wg mailing list
asciidoc-wg@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/asciidoc-wg