Menu

#3 Ability to join and break segments

future
open
None
5
2023-09-19
2004-06-11
No

(got the following request in OmegaT yahoo group
from Micah Bly)

Hello All. I am a new Omega T user ... I shamelessly
have some feature requests:

An option to be able to expand the current segment
rightwards, to include more, by removing a line break.
In case you had a line break in the wrong place. Even
when pre-editing files, sometimes these slip by you...

And opposite: ability to split a segment within the OT
environment. By adding a return code or by any other means.

Related

Feature Requests: #1547

Discussion

  • Maxym Mykhalchuk

    • summary: [RFE] Ability to join and break segments --> [?] Ability to join and break segments
     
  • Maxym Mykhalchuk

    Logged In: YES
    user_id=488500

    (it's undecided what timeframe is this RFE in)

     
  • Maxym Mykhalchuk

    • summary: [?] Ability to join and break segments --> [unknown] Ability to join and break segments
     
  • Maxym Mykhalchuk

    Logged In: YES
    user_id=488500

    This will require changing the engine at a rather low level
    - doable
    (I've a general idea on how) but not exactly trivial.

    Keith

     
  • Maxym Mykhalchuk

    • summary: [unknown] Ability to join and break segments --> [?] Ability to join and break segments
     
  • Maxym Mykhalchuk

    • summary: [?] Ability to join and break segments --> [unknown] Ability to join and break segments
     
  • Maxym Mykhalchuk

    • priority: 6 --> 7
    • summary: [unknown] Ability to join and break segments --> [1.5] Ability to join and break segments
    • assigned_to: keithgodfrey --> mihmax
    • milestone: --> 258669
    • status: open --> open-accepted
     
  • Maxym Mykhalchuk

    Logged In: YES
    user_id=488500

    This RFE is considered as a top issue for the next OmegaT
    release -- 1.5.

     
  • Maxym Mykhalchuk

    • milestone: 258669 -->
    • summary: [1.5] Ability to join and break segments --> Ability to join and break segments
    • status: open-accepted --> open
     
  • Maxym Mykhalchuk

    Logged In: YES
    user_id=488500

    Plans changed, the next OmegaT release - 2.0, is going to be
    fixing compatibility and memory footprint issues.

     
  • Jean-Christophe Helary

    • milestone: --> 442218
     
  • Jean-Christophe Helary

    • milestone: 442218 --> 258669
     
  • Didier Briel

    Didier Briel - 2007-11-04
    • assigned_to: mihmax --> nobody
    • milestone: 258669 -->
     
  • Marc Prior

    Marc Prior - 2008-02-27

    Logged In: YES
    user_id=722901
    Originator: NO

    I'm picking this RFE up because Samuel Murray has pointed out a way in which it could be implemented without radical changes to the architecture.

    RFE (I)

    When a new project is created, OmegaT creates a file <project>/omegat/segmentation.conf. This segmentation.conf behaves in the same way as <home>/.omegat/segmentation.conf. It is read by OmegaT at project load, and its break/exception rules take priority over those in the latter.

    A "Split segment at cursor point" control (1) is added to the UI. When actuated, it adds a new break rule to <project>/omegat/segmentation.conf to insert a segment break after the string {text preceding the cursor point in the active segment}. To use this function, the user must first have inserted the source text into the target text field (e.g. by selecting Editing behaviour > The source text).

    A "Merge segment with next" control (2) is added to the UI. When actuated, it adds a new break exception rule to <project>/omegat/segmentation.conf to suppress segment breaking after the string {current segment}.

    Both sub-functions require that the user reload the project.

    A control (3) undoes the merge or split operation by deleting the relevant break or exception in <project>/omegat/segmentation.conf.

    RFE (II)

    RFE (I) is the simplest implementation; it simply changes the segmentation rules so that the project is segmented differently when next loaded. RFE (II) extends its functionality by obviating the need for a project reload. When controls (1) or (2) are actuated, a pop-up editing window is launched containing only the affected segments. The merge or split operation is performed in exactly the same way, but within the pop-up editing window rather than in the main editing window.

    The user can then translate the affected segments directly in this window, without loading. They are then added to project_save.tmx. The segments remain unchanged in the main display, but OmegaT sets a flag to launch the pop-up editing window automatically whenever the segment concerned is opened in the current session.

     
  • Jean-Christophe Helary

    • priority: 7 --> 5
    • milestone: --> future
     
  • Didier Briel

    Didier Briel - 2009-07-12
    • assigned_to: nobody --> woerie
    • summary: Ability to join and break segments --> machine translation
     
  • Didier Briel

    Didier Briel - 2009-07-12
    • summary: machine translation --> Ability to join and break segments
     
  • Didier Briel

    Didier Briel - 2009-07-12

    The change of title was not intended.

    Didier

     
  • Thomas CORDONNIER

    I don't know whenever you saw it in the Yahoo list, but my clients required me to implement the solution "RFE (I)" in DGT-OmegaT. Feel free to test and make comments - the solution is not perfect so we would be happy to receive feedback to make it better. And if finally you want it for OmegaT 4, it won't be hard for me to do the conversion.

    Thomas

     
  • Jean-Christophe Helary

    Could this be considered temporarily implemented if we added Kos' script to the distribution ?

     
    • Aaron Madlon-Kay

      I would say no. A script is an informal solution, but I would keep the RFE open for a "formal" solution.

       
  • Jean-Christophe Helary

    Ok, so I'll put a RFE for including Kos' script with a link to this RFE.

     

Log in to post a comment.