Both source and target in final render
Thread poster: Pierret Adrien

Pierret Adrien  Identity Verified
China
Local time: 01:46
Chinese to French
+ ...
Mar 13, 2013

Hello,

I was wondering if there is any way I could get OmegaT to render both source and target text in output files ?

Thank you.


 

Samuel Murray  Identity Verified
Netherlands
Local time: 18:46
Member (2006)
English to Afrikaans
+ ...
Generally not without some rigmarole, but... Mar 13, 2013

Pierret Adrien wrote:
I was wondering if there is any way I could get OmegaT to render both source and target text in output files?


What exactly do you want the target file to look like after you're done?

I mean, do you want the output file to be a table, with the translation in the second column? Or do you want the translation of each sentence or each paragraph directly underneath the source text? Or do you want the translation of each sentence to follow the source text, perhaps in square brackets or something?



[Edited at 2013-03-13 07:07 GMT]


 

Pierret Adrien  Identity Verified
China
Local time: 01:46
Chinese to French
+ ...
TOPIC STARTER
Well, I guess I don't mind the actual pattern Mar 13, 2013

The most common pattern requirement I get from my clients is :

[Paragraph #1 Source]
[Paragraph #1 Target]

[Paragraph #2 Source]
[Paragraph #2 Target]

in a document.

Or

[Column #1 Source] [Column #2 Target]

in an Excel table, but this one can be handled quite easily manually.

I don't actually mind the pattern, since I have the feeling that once you get how it's done, if it's doable, you probably can tweak it the way you want.

I'm not much into coding, but I can get the logic and figure out issues if given directions.

Thank you.


 

John Holland  Identity Verified
France
Local time: 18:46
Member (2012)
French to English
Macro to create table from text? Mar 13, 2013

Hi, Pierret

Here's how I make bilingual documents using Writer, the word processor in LibreOffice, and OmegaT.
https://www.libreoffice.org/default

There's an extension for Writer called "Translation Table" which converts selected text to a two-column table with one sentence segment in each row of the left column of the table. It's kind of like the "covert text to table" command available in most word processors, but it has some additional features and involves clicking just one button so saves time.
http://extensions.libreoffice.org/extension-center/translation-table

When I want to make a bilingual document, I take the original document, use the "Translation Table" extension to make a table (which involves creating a new document - that's part of the extension). I translate this new document and generate the target document in OmegaT. Then I open the target in Writer and copy the translated text (the left column) to the right column of the new document with the table. It's now a bilingual document with source on the left matched with target on the right.

In addition to simplifying the process of creating the table, the extension has some nice features such as allowing the target language to be set when the table is created. It also allows for a monolingual document to be created at the end of the process in one click.

If you're not a LibreOffice (or OpenOffice.org) user, I bet it would be possible to do something like this with macros in other programs like MS Word.


 

Pierret Adrien  Identity Verified
China
Local time: 01:46
Chinese to French
+ ...
TOPIC STARTER
Very interesting, but Mar 15, 2013

This is very interesting, I am a MS Office user but mostly by habit, I'm not against a change.

Unfortunately I'm afraid this would not very convenient regarding my needs. I am not always translating plain text, but sometimes forms or other kinds of documents with heavy layout, and is required specifically to get a bilingual render.

So, a way of customizing the way OmegaT renders its target file would be best indeed, but I have no idea whether this is doable and how.

Just wondering, am I the only one with this kind of needs ?


 

Didier Briel  Identity Verified
France
Local time: 18:46
Member (2007)
English to French
+ ...
You could put both in the target segment Mar 15, 2013

Pierret Adrien wrote:
The most common pattern requirement I get from my clients is :

[Paragraph #1 Source]
[Paragraph #1 Target]

[Paragraph #2 Source]
[Paragraph #2 Target]

in a document.

Supposing you translate by paragraphs (without segmenting), you could put both source and target in the target segment.

Didier


 

Pierret Adrien  Identity Verified
China
Local time: 01:46
Chinese to French
+ ...
TOPIC STARTER
But I do segment Mar 20, 2013

But I guess that's okay, if that's not a feature i'll just find a workaround of some kind.

Thank you.


 

Samuel Murray  Identity Verified
Netherlands
Local time: 18:46
Member (2006)
English to Afrikaans
+ ...
Not really possible (even in other CAT tools, I suspect) Mar 20, 2013

Pierret Adrien wrote:
The most common pattern requirement I get from my clients is :

[Paragraph #1 Source]
[Paragraph #1 Target]

[Paragraph #2 Source]
[Paragraph #2 Target]

in a document.


Even if you use a CAT tool that segments by paragraph (OmegaT or something else), the tool's concept of "paragraph" may not be the same as yours. For example, most CAT tools that I have used will consider the following as five paragraphs, not one:

The rain in...
* Spain
* France
* Germany
...falls mainly on the plains.


If your client would be happy with a per-sentence duplication, then I have an AutoIt script that might be adapted to your needs. You could, for example, put every target sentence in square brackets, and then in MS Word use find/replace with wildcards to change all bracketed text into highlighted text. The script is not perfect -- if you have formatting across sentence boundaries, the formatting will be taken up by the entire translated sentence, e.g.:



Would this sort of thing interest you? If so, get the script here:
http://leuce.com/autoit/uncleanifyTMX.zip
You need to install AutoIt to make it work.

Samuel


 

Samuel Murray  Identity Verified
Netherlands
Local time: 18:46
Member (2006)
English to Afrikaans
+ ...
Use a two-column table? Mar 20, 2013

Pierret Adrien wrote:
The most common pattern requirement I get from my clients is :

[Paragraph #1 Source]
[Paragraph #1 Target]

[Paragraph #2 Source]
[Paragraph #2 Target]

in a document.


Say, what might work in some cases is if you convert the entire document to a table with 1 column, in which each paragraph is in a single cell. You may have to merge some cells manually later, e.g. if you have bullet lists that even MS Word will treat as separate "paragraphs". Then copy the translation into a second column, and then convert the entire table to text, using the "paragraph" setting instead of the "tab" setting (so that every cell is converted to below the previous one, and not next to it). This might actually work.


 

John Holland  Identity Verified
France
Local time: 18:46
Member (2012)
French to English
Two-column table Mar 20, 2013

Samuel Murray wrote:
Say, what might work in some cases is if you convert the entire document to a table with 1 column, in which each paragraph is in a single cell. You may have to merge some cells manually later, e.g. if you have bullet lists that even MS Word will treat as separate "paragraphs". Then copy the translation into a second column, and then convert the entire table to text, using the "paragraph" setting instead of the "tab" setting (so that every cell is converted to below the previous one, and not next to it). This might actually work.


That's just the kind of thing I thought could work.

One advantage to using a table in some way in the source document is that it makes aligning whatever needs to be aligned (sentences, paragraphs) so much easier.


 

Pierret Adrien  Identity Verified
China
Local time: 01:46
Chinese to French
+ ...
TOPIC STARTER
I'll have a try Mar 20, 2013

at those solutions and see how it turns out.

Thank you very much, I'll provide feedback.


 


There is no moderator assigned specifically to this forum.
To report site rules violations or get help, please contact site staff »


Both source and target in final render

Advanced search






SDL MultiTerm 2019
Guarantee a unified, consistent and high-quality translation with terminology software by the industry leaders.

SDL MultiTerm 2019 allows translators to create one central location to store and manage multilingual terminology, and with SDL MultiTerm Extract 2019 you can automatically create term lists from your existing documentation to save time.

More info »
SDL Trados Studio 2019 Freelance
The leading translation software used by over 250,000 translators.

SDL Trados Studio 2019 has evolved to bring translators a brand new experience. Designed with user experience at its core, Studio 2019 transforms how new users get up and running and helps experienced users make the most of the powerful features.

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search