Date   

chat@omegat.groups.io Group Guidelines (monthly reminder) #guidelines-notice

chat@omegat.groups.io Group Moderators <chat@...>
 

Group Guidelines

Please read before posting!
 
The chat@omegat.groups.io group is for asking and answering questions about OmegaT and similar programs, and for discussing topics that are related to OmegaT.

Groups.io vs. Sourceforge.net
There is a similar group of OmegaT enthusiasts called the "omegat-users" group at Sourceforge.net.  OmegaT also used to have a group at Yahoogroups.  The group at Yahoogroups was migrated to Sourceforge in late 2019.  The group at Sourceforge has more members than the group at Groups.io, and all of the old Yahoogroups messages are available in the Sourceforge group's archives, here: https://sourceforge.net/p/omegat/mailman/omegat-users/. However, some people find Groups.io more user-friendly, and Groups.io allows web posting, and that is the reason for this second OmegaT user group.  We recommend that you join both groups.

How to post a useful message
When asking a question, please don't forget to include the following information in your message:
  • Which version of OmegaT you are using (if any)
  • What is your operating system, and which version
  • What file types do your question relate to (if any)
It may also be useful to mention the "support information", which you can copy in OmegaT by going to Help > About, and clicking "Copy Support Info", which you can then paste into your e-mail.
 
 
Languages
Although Groups.io's user interface is currently available only in English, and although the group's guidelines etc. are in English, please feel free to use any language when posting messages in this group.  This is not an "English-only" group.
 
List policies
All new members start with moderated status -- their first message to the list will be moderated. 

Searching old messages
You can search the old Yahoogroups messages at the Sourceforge group, here: https://sourceforge.net/p/omegat/mailman/omegat-users/ (no login necessary).  To search the old messages that were posted at Groups.io, use the Messages section.


Re: [Omegat-users] Official twitter account

Jean-Christophe Helary
 

Thank you very much Charlotte.

Jean-Christophe

On Aug 24, 2020, at 21:52, Charlotte <charlottematou@...> wrote:

Hi Jean-Christophe,

I'm using the opportunity to give you a shoutout for the many times you
helped me on Twitter before I got on this mailing list. Thank you! I have
added an "omegaT" column in my Tweetdeck and will try and help you spotting
requests.

Best wishes,

Charlotte Matoussowsky
charlotte.matoussowsky@...
+33 (0)6 74 81 80 63
https://fr.linkedin.com/in/matoussowskycharlotte

-----Message d'origine-----
De : Jean-Christophe Helary <jean.christophe.helary@...>
Envoyé : lundi 24 août 2020 11:17
À : Mailing list for OmegaT user support
<omegat-users@...>
Cc : chat@omegat.groups.io
Objet : [Omegat-users] Official twitter account

Hello everybody.


Since the end of June, and for personal reason, I've been a lot less on the
web.

As far as the official twitter account is concerned (@OmegaTOfficial) I'm
still handling it but there are 2 issues:

1) The number of tweets that contain the string "omegat" and that are not
related to OmegaT is significant

2) The amount of time I can spend checking said tweets is limited


As far as the official account is concerned, I try to do the following:

1) Send a nice message to people who say they like or use OmegaT (like
"don't hesitate to ask any question")

2) Help when the tweet describes a problem the user has with OmegaT

3) Retweet stuff that is relevant to the community.

among other things.

When the tweet is in a language I do not understand (anything but French,
Japanese, English) the "Translate Tweet" function is usually enough to
understand it and react in a relevant manner.


Since Didier handed me the account, I think I've not done too bad and the
reactions are generally positive.


Now, I'd appreciate the following help:

If anyone finds a random tweet that is obviously related to OmegaT and to
which neither @OmegaTOfficial nor @brandelune have replied, please just
retweet or "forward" or do whatever so that I know the tweet exists, with a
tag to @OmegaTOfficial.

If you feel like helping or replying directly to the user, feel free to do
so. @OmegaTOfficial does not have to be the only active OmegaT related
twitter account. In fact, Didier handed me the account when he had to quit
because I was actively supporting users in Japanese under my personal
account: @brandelune.

I've noticed that Japanese users are more likely to use Twitter than other
language speakers, which is interesting, but there are a lot of Spanish
users (lots of students) and a number of other language speakers (Russian,
Arabic, etc.). It's quite interesting and fun to help them.


So just go ahead, no need for a green light or anything.

And thanks in advance.

--
Jean-Christophe Helary @brandelune
http://mac4translators.blogspot.com


Official twitter account

Jean-Christophe Helary
 

Hello everybody.


Since the end of June, and for personal reason, I've been a lot less on the web.

As far as the official twitter account is concerned (@OmegaTOfficial) I'm still handling it but there are 2 issues:

1) The number of tweets that contain the string "omegat" and that are not related to OmegaT is significant

2) The amount of time I can spend checking said tweets is limited


As far as the official account is concerned, I try to do the following:

1) Send a nice message to people who say they like or use OmegaT (like "don't hesitate to ask any question")

2) Help when the tweet describes a problem the user has with OmegaT

3) Retweet stuff that is relevant to the community.

among other things.

When the tweet is in a language I do not understand (anything but French, Japanese, English) the "Translate Tweet" function is usually enough to understand it and react in a relevant manner.


Since Didier handed me the account, I think I've not done too bad and the reactions are generally positive.


Now, I'd appreciate the following help:

If anyone finds a random tweet that is obviously related to OmegaT and to which neither @OmegaTOfficial nor @brandelune have replied, please just retweet or "forward" or do whatever so that I know the tweet exists, with a tag to @OmegaTOfficial.

If you feel like helping or replying directly to the user, feel free to do so. @OmegaTOfficial does not have to be the only active OmegaT related twitter account. In fact, Didier handed me the account when he had to quit because I was actively supporting users in Japanese under my personal account: @brandelune.

I've noticed that Japanese users are more likely to use Twitter than other language speakers, which is interesting, but there are a lot of Spanish users (lots of students) and a number of other language speakers (Russian, Arabic, etc.). It's quite interesting and fun to help them.


So just go ahead, no need for a green light or anything.

And thanks in advance.

--
Jean-Christophe Helary @brandelune
http://mac4translators.blogspot.com


Re: Font for specific projects

Dmitri Gabinski
 

You can create multiple configuration files/directories and launch
OmegaT with respective arguments as required.

https://omegat.sourceforge.io/manual-standard/en/chapter.installing.and.running.html#d0e596

ср, 27 мая 2020 г. в 22:53, M -- via groups.io
<testaferro7=yahoo.com@groups.io>:


Hello Community,


I have setup Omegat Projects in several languages. When I open our Laotian project, I need to change the font to make this project compatible with Laotian characters, otherwise, I would get corrupt characters (Menu Options>Preferences>Fonts.
If I open the Omegat project for Russian, I have to change the font to make it compatible with Russian characters. And this happens back and forth.

Is there a way to choose a font for specific projects without having to change it every time I open a project that requires a particular type of font?

Thanks!

Miguel


Font for specific projects

M --
 

Hello Community,


I have setup Omegat Projects in several languages. When I open our Laotian project, I need to change the font to make this project compatible with Laotian characters, otherwise, I would get corrupt characters (Menu Options>Preferences>Fonts.
If I open the Omegat project for Russian, I have to change the font to make it compatible with Russian characters. And this happens back and forth.

Is there a way to choose a font for specific projects without having to change it every time I open a project that requires a particular type of font?

Thanks!

Miguel


Re: [Omegat-users] Segmentation rule not working

M --
 

Looks like there is an extra space between the "v" and the backslash.

This: Indiv \.

Instead of this: Indiv\.


On Tuesday, May 5, 2020, 12:44:25 PM MDT, M -- <testaferro7@...> wrote:


Looks like there is an extra space between the "v" and the backslash.

This: Indiv \.

Instead of this: Indiv\.

On Tuesday, May 5, 2020, 11:59:20 AM MDT, Benjamin Brücker | proventis GmbH <b.bruecker@...> wrote:


Hi all,

OmegaT seems to ignore a segmentation rule I created.

Here is the German text I do not want to split after "Indiv."


The source code looks like that:

<li styleclass="Nummerierung"><text styleclass="Nummerierung" translate="true">Klicken Sie im Menü auf</text><text styleclass="Grossbuchstaben" translate="true"> Administration / Stammdaten / Indiv. Felder</text><text styleclass="Nummerierung" translate="true">.</text></li>

(Sorry for that ugly code. I'm sill impressed, that OmegaT is able to deal with Help- and Manual files.)
I have created a rule and put it on the first position:

After reloading or re-opening OmegaT, still splits up after "Indiv.". What is my mistake?

_______________________________________________
Omegat-users mailing list
Omegat-users@...
https://lists.sourceforge.net/lists/listinfo/omegat-users


Re: Segmentation of numbers

M --
 

Wonderful. It works great. Thank you very much Samuel!

On Tuesday, April 28, 2020, 3:55:36 AM MDT, Samuel Murray <samuelmurray@...> wrote:


On 27/04/2020 22:13, M -- via groups.io wrote:

> Please see the attached image. I did what you suggested but it doesn't
> seem to work unless I did something wrong.

1. According to your screenshots, your language pattern is still
"LN-CO", which is incorrect.

2. According to your screenshots, the rule you added is for "[0-9]\.",
which will match a number followed by a fullstop.  Your sample text's
numbers do not end on a fullstop.

So, in the rule set, change the language pattern from this:

LN-CO

to this:

.*

and in the rule itself, change this:

[0-9]\.

to this:

[0-9]

and then reload the project (F5).


Samuel



Re: Segmentation of numbers

Samuel Murray
 

On 27/04/2020 22:13, M -- via groups.io wrote:

Please see the attached image. I did what you suggested but it doesn't seem to work unless I did something wrong.
1. According to your screenshots, your language pattern is still "LN-CO", which is incorrect.

2. According to your screenshots, the rule you added is for "[0-9]\.", which will match a number followed by a fullstop. Your sample text's numbers do not end on a fullstop.

So, in the rule set, change the language pattern from this:

LN-CO

to this:

.*

and in the rule itself, change this:

[0-9]\.

to this:

[0-9]

and then reload the project (F5).

Samuel


Re: Segmentation of numbers

M --
 


Hi Samuel,

Please see the attached image. I did what you suggested but it doesn't seem to work unless I did something wrong.

You have to change the "Language Pattern" to ".*".  A fullstop followed
by an asterisk.

Right now, the language pattern is "LN-CO", which means that OmegaT will
only follow the rule if your project's source language is "LN-CO", which
it isn't. :-)  The characters ".*" tells OmegaT to use the rule for all
languages and all file types

On Thursday, April 23, 2020, 3:03:03 PM MDT, M -- <testaferro7@...> wrote:


Hi Samuel,

Please see the attached image. I did what you suggested but it doesn't seem to work unless I did something wrong.

It should be:

791 Chambers Road

453 E.Colfax Avenue

Instead, numbers followed by capitalized words, break segments in two.

This file is totally clean, it doesn't have any strange characters between numbers and capitalized words.

Let me know what you think.
Thanks
Miguel


Inline image



On Thursday, April 23, 2020, 9:52:12 AM MDT, M -- via groups.io <testaferro7@...> wrote:


Thank you very much Jean-Christophe and Samuel for your time. I willt try to follow Samel instructions. Hopefully, this issue is resolved in future versions.

Take care

Miguel

On Thursday, April 23, 2020, 2:02:56 AM MDT, Jean-Christophe Helary <jean.christophe.helary@...> wrote:




> On Apr 23, 2020, at 16:26, Samuel Murray <samuelmurray@...> wrote:
>
> On 22/04/2020 23:52, M -- via groups.io wrote:
>
>> I have a problem with the segmentation of numbers. I have something like this:
>> *24<segment 01>*
>> *Hour National Crisis Line<segment 02>
>
> I tested this on a plain text file, and I confirm that this happens.
>
> My guess is that the default segmentation rules assume that a number at the start of a line, followed by a capital letter, is meant to be a line number or a heading number.

That's correct. I seem to remember having added that a long time ago...

before: ^\s*\p{Nd}+[\p{Nd}\.\)\]]+

^\s*        string beginning with zero or more white space
\p{Nd}+        followed by one or more "digit zero through nine in any script except ideographic scripts"
[\p{Nd}\.\)\]]+    followed one of more of "digit zero through nine in any script except ideographic scripts" or literal "." or literal ")" or literal "]"

after: \s+\p{Lu}

s+        one or more white space
\p{Lu}        followed by an uppercase letter that has a lowercase variant





>  I tried to google for the meaning of the four general rules in OmegaT, but I was unable to find a sufficiently comprehensive guide... and the link to the Java documentation in the OmegaT user manual is dead.


Oh. We need to fix this.

My suggestion was WRONG, sorry. There needs to be a NON BREAKABLE SPACE there to fix the segmentation for that segment only.


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune



Re: Segmentation of numbers

Samuel Murray
 

On 23/04/2020 23:03, M -- via groups.io wrote:

Please see the attached image. I did what you suggested but it doesn't seem to work unless I did something wrong.
You have to change the "Language Pattern" to ".*". A fullstop followed by an asterisk.

Right now, the language pattern is "LN-CO", which means that OmegaT will only follow the rule if your project's source language is "LN-CO", which it isn't. :-) The characters ".*" tells OmegaT to use the rule for all languages and all file types.

Samuel


Re: Segmentation of numbers

M --
 

Hi Samuel,

Please see the attached image. I did what you suggested but it doesn't seem to work unless I did something wrong.

It should be:

791 Chambers Road

453 E.Colfax Avenue

Instead, numbers followed by capitalized words, break segments in two.

This file is totally clean, it doesn't have any strange characters between numbers and capitalized words.

Let me know what you think.
Thanks
Miguel


Inline image



On Thursday, April 23, 2020, 9:52:12 AM MDT, M -- via groups.io <testaferro7@...> wrote:


Thank you very much Jean-Christophe and Samuel for your time. I willt try to follow Samel instructions. Hopefully, this issue is resolved in future versions.

Take care

Miguel

On Thursday, April 23, 2020, 2:02:56 AM MDT, Jean-Christophe Helary <jean.christophe.helary@...> wrote:




> On Apr 23, 2020, at 16:26, Samuel Murray <samuelmurray@...> wrote:
>
> On 22/04/2020 23:52, M -- via groups.io wrote:
>
>> I have a problem with the segmentation of numbers. I have something like this:
>> *24<segment 01>*
>> *Hour National Crisis Line<segment 02>
>
> I tested this on a plain text file, and I confirm that this happens.
>
> My guess is that the default segmentation rules assume that a number at the start of a line, followed by a capital letter, is meant to be a line number or a heading number.

That's correct. I seem to remember having added that a long time ago...

before: ^\s*\p{Nd}+[\p{Nd}\.\)\]]+

^\s*        string beginning with zero or more white space
\p{Nd}+        followed by one or more "digit zero through nine in any script except ideographic scripts"
[\p{Nd}\.\)\]]+    followed one of more of "digit zero through nine in any script except ideographic scripts" or literal "." or literal ")" or literal "]"

after: \s+\p{Lu}

s+        one or more white space
\p{Lu}        followed by an uppercase letter that has a lowercase variant





>  I tried to google for the meaning of the four general rules in OmegaT, but I was unable to find a sufficiently comprehensive guide... and the link to the Java documentation in the OmegaT user manual is dead.


Oh. We need to fix this.

My suggestion was WRONG, sorry. There needs to be a NON BREAKABLE SPACE there to fix the segmentation for that segment only.


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune



Re: Segmentation of numbers

M --
 

Thank you very much Jean-Christophe and Samuel for your time. I willt try to follow Samel instructions. Hopefully, this issue is resolved in future versions.

Take care

Miguel

On Thursday, April 23, 2020, 2:02:56 AM MDT, Jean-Christophe Helary <jean.christophe.helary@...> wrote:




> On Apr 23, 2020, at 16:26, Samuel Murray <samuelmurray@...> wrote:
>
> On 22/04/2020 23:52, M -- via groups.io wrote:
>
>> I have a problem with the segmentation of numbers. I have something like this:
>> *24<segment 01>*
>> *Hour National Crisis Line<segment 02>
>
> I tested this on a plain text file, and I confirm that this happens.
>
> My guess is that the default segmentation rules assume that a number at the start of a line, followed by a capital letter, is meant to be a line number or a heading number.

That's correct. I seem to remember having added that a long time ago...

before: ^\s*\p{Nd}+[\p{Nd}\.\)\]]+

^\s*        string beginning with zero or more white space
\p{Nd}+        followed by one or more "digit zero through nine in any script except ideographic scripts"
[\p{Nd}\.\)\]]+    followed one of more of "digit zero through nine in any script except ideographic scripts" or literal "." or literal ")" or literal "]"

after: \s+\p{Lu}

s+        one or more white space
\p{Lu}        followed by an uppercase letter that has a lowercase variant





>  I tried to google for the meaning of the four general rules in OmegaT, but I was unable to find a sufficiently comprehensive guide... and the link to the Java documentation in the OmegaT user manual is dead.


Oh. We need to fix this.

My suggestion was WRONG, sorry. There needs to be a NON BREAKABLE SPACE there to fix the segmentation for that segment only.


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune



Re: Segmentation of numbers

Jean-Christophe Helary
 

On Apr 23, 2020, at 16:26, Samuel Murray <@ugcheleuce> wrote:

On 22/04/2020 23:52, M -- via groups.io wrote:

I have a problem with the segmentation of numbers. I have something like this:
*24<segment 01>*
*Hour National Crisis Line<segment 02>
I tested this on a plain text file, and I confirm that this happens.

My guess is that the default segmentation rules assume that a number at the start of a line, followed by a capital letter, is meant to be a line number or a heading number.
That's correct. I seem to remember having added that a long time ago...

before: ^\s*\p{Nd}+[\p{Nd}\.\)\]]+

^\s* string beginning with zero or more white space
\p{Nd}+ followed by one or more "digit zero through nine in any script except ideographic scripts"
[\p{Nd}\.\)\]]+ followed one of more of "digit zero through nine in any script except ideographic scripts" or literal "." or literal ")" or literal "]"

after: \s+\p{Lu}

s+ one or more white space
\p{Lu} followed by an uppercase letter that has a lowercase variant




I tried to google for the meaning of the four general rules in OmegaT, but I was unable to find a sufficiently comprehensive guide... and the link to the Java documentation in the OmegaT user manual is dead.
Oh. We need to fix this.

My suggestion was WRONG, sorry. There needs to be a NON BREAKABLE SPACE there to fix the segmentation for that segment only.


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune


Re: Segmentation of numbers

Samuel Murray
 

On 22/04/2020 23:52, M -- via groups.io wrote:

I have a problem with the segmentation of numbers. I have something like this:
*24<segment 01>*
*Hour National Crisis Line<segment 02>
I tested this on a plain text file, and I confirm that this happens.

My guess is that the default segmentation rules assume that a number at the start of a line, followed by a capital letter, is meant to be a line number or a heading number. I tried to google for the meaning of the four general rules in OmegaT, but I was unable to find a sufficiently comprehensive guide... and the link to the Java documentation in the OmegaT user manual is dead.

What you can do, is add a new rule above all other rules.

- In OmegaT, go Options > Segmentations.
- In the top part of the dialog, click Add. This will add a new set of rules, usually called "New Language and Country" and "LN-CO". Rename this to e.g. "Fixes" and ".*".
- Select the Fixes rule set and then click Move Up until the rule set is at the very top of the list.
- Then, while Fixes is selected, in the bottom part of the dialog, click "Add". This will add a new segmentation rule. Edit that rule as follows:

Break/Exception: unticked
Pattern Before: [0-9]
Pattern After: \s

This rule means that (apart from certain exceptions) no segment will ever break between a number and a space. I'm not sure if this will affect numbers followed by tabs.

Samuel


Re: Segmentation of numbers

Dmitri Gabinski
 

1. Show the file. 
2. Show your segmentation.conf. 


Re: Segmentation of numbers

Jean-Christophe Helary
 

Hello Miguel,

The easiest way to deal with such rogue segments is to go to your original file, make sure that the thing between "24" and "Hour National Crisis Line" is really a space (erase the current space and add a new "standard" one) and reload.

If that still doesn't work you can start to worry about rogue segmentation rules :)

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune

On Apr 23, 2020, at 6:52, M -- via groups.io <testaferro7=yahoo.com@groups.io> wrote:

Hello all,

I have a problem with the segmentation of numbers. I have something like this:

24<segment 01>
Hour National Crisis Line<segment 02>


When in fact, it should be:
24 Hour National Crisis Line<segment 01>

There is no line break after the number 24, all the hidden tags (if any) have been cleaned with "Document Cleaner" inTranstools.

I haven't found a way to make it work using the Segmentation Setup within Omegat. Any ideas. I am not a Regex expert.

It does work well if I change "Hour" to "hour". Then I have the correct segmentation: 24 hour National Crisis Line<segment 01>
However, I would prefer not to touch the original file to make changes like this.

I don't have this problem when numbers are in the middle of a sentence, only at the beginning.

My OS is Windows 10 and I work with OMEGAT 5.2.

Thanks a lot!

Miguel


Segmentation of numbers

M --
 

Hello all,

I have a problem with the segmentation of numbers. I have something like this:

24<segment 01>
Hour National Crisis Line<segment 02>


When in fact, it should be:
24 Hour National Crisis Line<segment 01>

There is no line break after the number 24, all the hidden tags (if any) have been cleaned with "Document Cleaner" inTranstools.

I haven't found a way to make it work using the Segmentation Setup within Omegat. Any ideas. I am not a Regex expert.

It does work well if I change "Hour" to "hour". Then I have the correct segmentation: 24 hour National Crisis Line<segment 01>
However, I would prefer not to touch the original file to make changes like this.

I don't have this problem when numbers are in the middle of a sentence, only at the beginning.

My OS is Windows 10 and I work with OMEGAT 5.2.

Thanks a lot!

Miguel


creating TM by ALIGNMENT on Omega T

cinziacroatto@...
 

Hello, 
I am new to Omega T and am trying to create some TMX by aligning old translations. However, even if I put the TMX file I created into the TM/auto folder of the new project, I get no fuzzy matches at all, although there should be plenty. I can't understand what I'm doing wrong. Can someone advise please. 
Thanks in advance
Cinzia


test

Samuel Murray
 

test


test

Samuel Murray
 

test