> containing two sentences in some cases, but that is not normally a > segmentation rule more conservative so that it does not split before I would go further still and make your default sentence That's obviously a rule I would have to put in place, an > and then simply reload the project (the shortcut is F5). > That's correct, but you can modify the segmentation rules at any time didn't work either.Ĭan anyone advise what I'm missing as I can't help but feel it's so Note: Exception rule - see the use of ? in regular expressionsĪgain, creating a rule II?\. I tried the above (created a rule III\.) with the an "after" of \s, but Note: This is an exception rule, so the rule check box must not be ticked. OmT no matter what rule I try to put in place.Ĭonsulting the docs, I found the following: Second, however, causes a line break between "III." and "Batallion" in The first caused no line splitting, which was exactly correct. Translation of some documents about the invasion of Normandy, I wasĮncountering German abbreviations such as these: If I may give an example from a recent project: while working on a Looked at the documentation and tried some of the suggestions, but so I have to say I don't understand how segmentation rules work. That's obviously a rule I would have to put in place, an exception for "Ch." 7", which is short for "Chapter 7" in French. > That last time, it split because it said "Ch. > That's what I suspected, there's no merging segments after it's been loaded into the project. There are ways of maintaining multiple sets of segmentation rules, If you change the rules and then reload an old project, it may then be Language, even in future projects, until you change them again. > Does OmegaT save the rule for good, or does it depend on each project?
This may lead to a segmentĬontaining two sentences in some cases, but that is not normally a Segmentation rule more conservative so that it does not split before That's correct, but you can modify the segmentation rules at any timeĪnd then simply reload the project (the shortcut is F5). > That's what I suspected, there's no merging segments after it's been If it was due to a return, then just edit the source and remove the return and then reload the project. > I find that I sometimes need to prep my files due to people putting in hard returns in a sentence. > As mentioned by Marc, there is no command to bring together two segments. That's obviously a rule I would have to put in place, an exception for "Ch."ĭoes OmegaT save the rule for good, or does it depend on each project? That last time, it split because it said "Ch. That's what I suspected, there's no merging segments after it's been loaded into the project.
> Bug reports, feature requests, OmegaT test versions etc.: > OmegaT localizers should join the "omegat-l10n" group > OmegaT contributors should join the "omegat-development" group > One question: Is it possible to merge two adjacent segments, that are actually the same sentence, but OmegaT splits as if two? > I'm new to OmegaT and new on the message board, so learning the basics. If OmegaT splits a single sentence into two segments, you There is no "merge adjacent segments" as such, but there are
One question: Is it possible to merge two adjacent segments, that are actually the same sentence, but OmegaT splits as if two?
0 kommentar(er)
