[ omegat-Feature Requests-1587729 ] Identify subflow segments visually

[SourceForge.net <no...@so...>]

Feature Requests item #1587729, was opened at 2006-10-31 09:27
Message generated for change (Settings changed) made by didierbr
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=1587729&group_id=68187

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: future
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jean-Christophe Helary (brandelune)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Identify subflow segments visually

Initial Comment:
An ODF file may contain a number of fields including comments _for_ the 
translator, inserted as notes.

OmegaT does not make any difference in the display and sometimes 
such segments are translated by mistake because they look like 
translatable text.

OmegaT should indicate what is the origine of the segment, maybe by 
using a different segment tag.

<segment 0001> for normal segments
<subflow 0001> for not visible segments

----------------------------------------------------------------------

Comment By: Jean-Christophe Helary (brandelune)
Date: 2006-11-11 00:30

Message:
Logged In: YES 
user_id=915082

I don't think changing the numbering scheme is of much importance. What
matters (and that is a documentation issue :) is that users 
recognize such tags as "special" items.

----------------------------------------------------------------------

Comment By: Henry Pijffers (henry_pijffers)
Date: 2006-11-10 22:08

Message:
Logged In: YES 
user_id=545103

Right, that type of segments... I was thinking about
something completely different. Never mind.

So, you're suggesting a different segment tag. That might be
possible, if the filters could indicate to OmegaT whether
something is a segment or a subsegment.

However, I'm unsure about the numbering. Even though we
could probably work out the position of a subsegment in a
segment (whether it's the 1st, 2nd, 3rd, etc.), by just
assuming they appear in order after the main segment, we
couldn't just renumber them 1, 2, 3..., because that would
create vacancies in the numbering of the main segments
(cause they are all taken together in one list).

----------------------------------------------------------------------

Comment By: Jean-Christophe Helary (brandelune)
Date: 2006-11-10 00:25

Message:
Logged In: YES 
user_id=915082

some attributes _are_ translatable contents and especially in HTML can be
necessary for the proper localization of a file.

----------------------------------------------------------------------

Comment By: Henry Pijffers (henry_pijffers)
Date: 2006-11-08 15:45

Message:
Logged In: YES 
user_id=545103

If they're not visible, why are we translating them anyway?
Wouldn't it be better if OmegaT skipped them altogether?
Dunno whether that's possible...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=1587729&group_id=68187