No "Fragment Alignment" setting in server-based TMs

Hi

When opening server-based TMs on a GroupShare 2017 SR1 server, I don't see the settings level "Fragment Alignment", which is present in the settings of file-based TMs.

Is this on purpose or a bug?  

Where do we change the settings for Fragment Alignment for such TMs?

The only indication that the TM is upLIFT-enabled is this indication in the GS web-based management console:

Screenshot showing upLIFT alignment status with a discrepancy: 24,368 of 14,600 Translation units unaligned.

.. although this also sounds weird, it always shows more unaligned units than there are units in total?!?

I hope, someone can shed some light on this.

Walter



Generated Image Alt-Text
[edited by: Trados AI at 6:31 AM (GMT 0) on 5 Mar 2024]
emoji
Parents
  • Hi Walter,

    The settings not being exposed in Studio is by design. We want the GroupShare upLIFT functionality to be a seamless as possible, i.e. every Groupshare TM is upLIFT enabled and you don't have to worry about settings or triggering it manually. As it's a server we can do this automatically in the background vs. a file-based TM.
    The settings for search that are in Studio (i.e. how many fragments to search for etc.) are valid for both file and server-based TMs.

    The unaligned value being higher than the TU count is very likely related to a recent import. By default GS 2017 SR1 refreshes the TU count every 10 minutes and not in real-time to reduce the impact on performance. So if you check that TM 10 minutes later, the TUs are likely higher again.

    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |

Reply
  • Hi Walter,

    The settings not being exposed in Studio is by design. We want the GroupShare upLIFT functionality to be a seamless as possible, i.e. every Groupshare TM is upLIFT enabled and you don't have to worry about settings or triggering it manually. As it's a server we can do this automatically in the background vs. a file-based TM.
    The settings for search that are in Studio (i.e. how many fragments to search for etc.) are valid for both file and server-based TMs.

    The unaligned value being higher than the TU count is very likely related to a recent import. By default GS 2017 SR1 refreshes the TU count every 10 minutes and not in real-time to reduce the impact on performance. So if you check that TM 10 minutes later, the TUs are likely higher again.

    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |

Children
No Data