How to indicate that a row in Excel corresponds to an ICE Segment

Technical Support
1

Hi everyone,

I am currently working with a client proprietary online CAT tool that only allows to export bilingual files in Excel format.

When you open the Excel file, it appears as follows:

imagen
imagen1115×420 4.94 KB

I replaced the content in source and target text columns with “Source Text” and “Target Text”, respectively, to avoid NDA breach, but the idea is there.

As you can see, column A contains the source text, column B the target and column C the match type (CM, 100% or AT).

Since CM (context matches or “ICE Segments”) are out of the scope, my question is: is there any way to tweak this Excel file so that Xbench recognizes those CM strings as ICE Segments and I can exclude them from checks?

I tried replacing “CM” with “ICE” or “101%” to see if I could get some dumb luck, but as expected, it did not work :sweat_smile:. I know I could just delete all those CM rows, but for the consistency checks and context, it would be great if I could preserve those rows and just check/uncheck the “Exclude ICE Segments” box as required. Any ideas?

Kind regards,

Manuel

2

Hi Manuel,

That’s an interesting question. I don’t know how to get XBench to recognise these as ICE segments.
As an alternative, two ideas came to my mind:

  • hiding these rows in the Excel files > not sure if Xbench will then exclude them from the view
  • adding the word ICE at the beginning of the source text in all the ICE rows in Excel and then, with a Power Search in Xbench, excluding all rows containing that word from the QA.

Hope this can help :slight_smile: .

1 Like
3

Hi @C_Lechuga,

Thank you for your answer. Hiding those rows won’t work. I already tried that, but XB recognizes all the content in an Excel file, be it hidden or not.

Your other suggestion might help to recognize those strings more easily in the QA and discard them from checks, since it is not possible to exclude them through a Power Search in QA. It is not the best solution, but as a workaround, it might help to streamline the process a bit. Thank you!

@pcondal and @omartin, I know this is rather specific, but perhaps this issue with match type filtering could be taken into account for a future build?

Kind regards,

Manuel

4

As a workaround, you could use a macro for Excel that looks for those values in that column and deletes the row. Then, save a copy of the file and add it to your project for QA.

This macro generated by copilot looks for “CM” in column C. If the value is “CM”, it will delete the row. Please note that I have not tested it.

Sub DeleteCMRows()
    Dim ws As Worksheet
    Dim lastRow As Long
    Dim i As Long

    Set ws = ActiveSheet
    lastRow = ws.Cells(ws.Rows.Count, "C").End(xlUp).Row

    ' Loop from bottom to top to avoid skipping rows
    For i = lastRow To 1 Step -1
        If ws.Cells(i, "C").Value = "CM" Then
            ws.Rows(i).Delete
        End If
    Next i
End Sub
1 Like
5

Thank you, @omartin!

Good idea. Will test it and modify it if applicable. It will undoubtedly be faster than doing it manually.

Kind regards,