Not Considering

TM Fusion for Trados: Add system fields info

It would be great to have  TU system fields (creation user, creation date, usage count, etc.  ) in in the right coner like in Studio.

Screenshot of RWS AppStore Ideas 'Custom Fields' window with columns for Name and Value, showing fields like Quality, SourceFile, TargetFile, Status, and Text Field. A green box highlights the bottom right corner.

Yuriy Belik
Parents

  •  we accepted this one into development for some time in the future.  In the meantime I guess you could use this to get a neat table with readable source and target texts containing all the relevant system fields:

    SELECT 
    id, 
    substr(source_segment, instr(source_segment, '<Value>') + 7, instr(source_segment, '</Value>') - instr(source_segment, '<Value>') - 7) AS source_segment_text, 
    substr(target_segment, instr(target_segment, '<Value>') + 7, instr(target_segment, '</Value>') - instr(target_segment, '<Value>') - 7) AS target_segment_text, 
    creation_date, 
    creation_user, 
    change_date, 
    change_user, 
    last_used_date, 
    last_used_user, 
    usage_counter, 
    insert_date
FROM 
    translation_units;

    Then you could also export to a tab separate file for example where it might be useful for quickly identifying TUs based on easier, visual,  filtering perhaps.

Comment

  •  we accepted this one into development for some time in the future.  In the meantime I guess you could use this to get a neat table with readable source and target texts containing all the relevant system fields:

    SELECT 
    id, 
    substr(source_segment, instr(source_segment, '<Value>') + 7, instr(source_segment, '</Value>') - instr(source_segment, '<Value>') - 7) AS source_segment_text, 
    substr(target_segment, instr(target_segment, '<Value>') + 7, instr(target_segment, '</Value>') - instr(target_segment, '<Value>') - 7) AS target_segment_text, 
    creation_date, 
    creation_user, 
    change_date, 
    change_user, 
    last_used_date, 
    last_used_user, 
    usage_counter, 
    insert_date
FROM 
    translation_units;

    Then you could also export to a tab separate file for example where it might be useful for quickly identifying TUs based on easier, visual,  filtering perhaps.

Children