Context for alternative translations in Markdown files in OmegaT

9 views
Skip to first unread message

Manuel Souto Pico

unread,
May 1, 2021, 1:25:40 PM5/1/21
to okapi-users
Dear all,

I've been using the Okapi filter for Markdown in OmegaT... I have a question about alternative translations.

When I create one, the multiple translations pane shows something like the following:

Alternative translation blabla.

That one corresponds to the third segment in that file.

I was surprised to see that, as I was expecting the usual prev/next context, e.g.

Alternative translation blabla.
<filename.md>
(Previous se… <...> Next segm …)

Instead of that, it seems the filter is using some kind of segment ID, as it happens with XLIFF files.

I was wondering if someone could explain how it works, what is the business logic, and whether there's something in this functionality that is markdown specific or whether it could be applied to any other file type.

In OmegaT, the prev/next context when creating alternative translations is clearly insufficient for formats without segment IDs (i.e. other than XLIFF). Often more context is needed. See this thread about that: https://omegat.sourceforge.io/user-support-archive/2018-May/042446.html

It would be great if this approach could be used with other file types other than markdown.

Thanks in advance.

I am using okapiFiltersForOmegaT-1.8-1.40.0-capstan.jar in OmegaT 5.4.4.

Cheers, Manuel


Manuel Souto Pico

unread,
May 26, 2021, 8:21:18 AM5/26/21
to okapi-users
Dear all,

I have come across a bug in the functionality referred to in my previous email: https://bitbucket.org/okapiframework/okapi/issues/1065/alternative-translations-do-not-work-for

I hope it can be fixed soon! Let me know if I can help with anything else.

Cheers, Manuel

Manuel Souto Pico

unread,
Jun 8, 2021, 8:59:52 AM6/8/21
to okapi-users
Dear all,

Is there anything I can do to encourage the processing of this ticket ( https://bitbucket.org/okapiframework/okapi/issues/1065/alternative-translations-do-not-work-for ) or to bring attention to it?

It would be great if some developer could confirm that this is indeed a valid ticket for the Okapi filter (whether the issue can be fixed at that level). Or should I rather create a ticket for OmegaT instead?

Thanks in advance.

Cheers, Manuel



Manuel Souto Pico <termin...@gmail.com> escreveu no dia quarta, 26/05/2021 à(s) 14:20:
Dear all,

I have come across an issue in the functionality referred to in my previous email: https://bitbucket.org/okapiframework/okapi/issues/1065/alternative-translations-do-not-work-for
Reply all
Reply to author
Forward
0 new messages