Merging segments using quick-fix segmentation rules Tópico cartaz: Nina Halperin
|
|---|
Hello,
I seem to have more trouble creating "quick-fix segmentation rules" to merge segments than to split them, for some odd reason. OmegaT has created the following two segments that should be just one (also, talk about tag soup!):
Health[t0/]/[t1/]Developmenta[t2/]l:[t3/] [t4/]On August[t5/] 20[t6/], 2019[t7/],[t8/] [t9/]
Steve's parents[t10/], [t11/]Mr. and Mrs. Douglas completed an updated health and developmental questionnaire.
I created ... See more Hello,
I seem to have more trouble creating "quick-fix segmentation rules" to merge segments than to split them, for some odd reason. OmegaT has created the following two segments that should be just one (also, talk about tag soup!):
Health[t0/]/[t1/]Developmenta[t2/]l:[t3/] [t4/]On August[t5/] 20[t6/], 2019[t7/],[t8/] [t9/]
Steve's parents[t10/], [t11/]Mr. and Mrs. Douglas completed an updated health and developmental questionnaire.
I created the following "quick-fix rule" under "Properties" and then "Segmentation":
Pattern before: "[t9/]"
Pattern after: " Steve's" (with a space before the word "Steve's")
Break/exception *not* checked
This did not work. There are no hidden section breaks in this case (as this was a problem that I brought up in another example under a different forum). Am I formatting the segmentation rule incorrectly? Thanks for any tips!
[Edited at 2020-07-25 01:49 GMT] ▲ Collapse
| | | | Samuel Murray 
Holanda
Local time: 06:22
Membro (2006)
inglês para africâner
+ ...
Nina Halperin wrote:
I created the following "quick-fix rule" under "Properties" and then "Segmentation"...
I can't really help, except to say that (a) I don't think you can put tags in the segmentation rules and (b) under normal circumstances, the text you mention should not have been split into two segments, so there must be something that causes the split. If you want, you can send me the source file to look at (via e-mail).
| | | | Nina Halperin
Peru
Local time: 00:22
espanhol para inglês
+ ...
CRIADOR(A) DO TÓPICO | Tags shouldn't be a problem | Jul 25, 2020 |
Hi Samuel, the tags should not be a problem. In this tutorial, the guy puts a tag in the segmentation rules: https://www.youtube.com/watch?v=hHT9aHZciVU. While the tutorial is for splitting and not merging segments, I don't see why you could put tags in one and not the other.
Thank you so much, that is a lovely offer! I will message you.
| | | | Samuel Murray
Holanda
Local time: 06:22
Membro (2006)
inglês para africâner
+ ...
Nina Halperin wrote:
I created the following "quick-fix rule" under "Properties" and then "Segmentation":
Pattern before: "[t9/]"
Pattern after: " Steve's" (with a space before the word "Steve's")
Break/exception *not* checked
Why do you put a space before "Steve's"? Is there a space after [t9/] in the editor in OmegaT?
| | |
|
|
|
Nina Halperin
Peru
Local time: 00:22
espanhol para inglês
+ ...
CRIADOR(A) DO TÓPICO
There is no space after [t9/], but in this video about merging segments in OmegaT, the guy says you need to put in a space: https://www.youtube.com/watch?v=YYlHh11i664. Perhaps it is so that there is a space between the word at the end of the first segment and the word at beginning of the second segment? Even if I take out the space in the segmentation rule I added, the segments still do not ... See more There is no space after [t9/], but in this video about merging segments in OmegaT, the guy says you need to put in a space: https://www.youtube.com/watch?v=YYlHh11i664. Perhaps it is so that there is a space between the word at the end of the first segment and the word at beginning of the second segment? Even if I take out the space in the segmentation rule I added, the segments still do not merge in OmegaT.
[Edited at 2020-07-27 19:20 GMT] ▲ Collapse
| | | | Não há um moderador designado especificamente para este fórum. Para reportar violações às regras do site ou para obter ajuda, favor contatar a equipe do site » Merging segments using quick-fix segmentation rules | Anycount & Translation Office 3000 | Translation Office 3000
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info » |
| | Trados Business Manager Lite | Create customer quotes and invoices from within Trados Studio
Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
