Text missing after footnotes (Studio 2015 SR3, Word 2007-2016 filter)

Dear SDL team,

We have recently noticed a worrying pattern where, using the latest Word filter, sentences located after a footnote occasionally do not get imported into Studio and are not offered for translation. When the translated document is generated, those sentences do appear, but they remain in the source language.

I attach a snippet of one of the documents where we have noticed this issue, with the sentences skipped by Studio highlighted in yellow for ease of reference. I can share other files affected by this issue by e-mail if needed.

I have noticed several questions concerning a similar problem in Studio 2017, but nothing on Studio 2015. We are using Studio 2015 SR3 (build 12.3.5262.0) which, as I understand it, should already include CU7, which reportedly fixed an issue where footnotes were not getting imported.

Is there a fix for this problem for Studio 2015, or at the very least a way to anticipate when it's likely to occur? This issue is particularly worrying for us as many of the documents we work with include footnotes, and painstakingly checking large translated documents for untranslated sentences would be a huge drain in our resources.

Best,

Fran

SAMPLE2_HL.docx

Parents Reply Children
  • Hi Paul,

    Thanks for taking a look. It's weird that you cannot open it at all on Studio 2015 — just thought I'd add I'm using the "WordprocessingML v. 2" file type, if it's any help figuring out the problem. I can also share the SDLXLIFF file if you'd like to have a look inside.

    In any case, please do keep me posted about your findings. This issue is rather worrying for us and we'd really like to get to the bottom of the problem.

    Cheers,

    Fran
  • I can't even prep the provided file in Studio 2015. Studio seems to simply stop working. My 2015 is SR3 - 12.3.5181.10 which is slightly different than users.

     

    Unknown said:
    Is there a fix for this problem for Studio 2015, or at the very least a way to anticipate when it's likely to occur?

     

    Since your version of Studio 2015 can work with Word files, I would like to offer a quick QA step you can do while the issue is being looked at.

    1. When you create a new project, make a habit of adding an extra language for QA step.
    2. This extra language can be anything, but I would suggest that is something clear to anyone who might open your project that it is a language for QA, something you've never come across as a target language for example.
    3. Prep as usual and complete project creation wizard.
    4. Go to Files and choose the extra language for QA.
    5. Run a custom batch task and choose Pseudo-translate, Generate Target Translations
    6. In Batch Processing option for Pseudo-translate task, make sure to modify the settings as follows.
      • Check the box for Append characters to the start: $1$2$
      • Check the box for Append characters to the end: $3$4$
      • Choose Apply pseudo-translate from the dictionary
    7. Open the generated target in MS Word.
    8. On the Home tab, in the Editing group, click the arrow next to Find, and then click Advanced Find.
    9. Go to Replace tab and click More >> and make sure to modify the settings as follows. 
      • Find what: $1$2$?@$3$4$
      • Replace with: (null, empty, nothing)
      • Check Use wildcards
    10. Click Replace All
    11. If you see any text other than whitespace left, that would indicate the text did not get extracted by Studio.

     

     

    Thank you,

    Naoko

  • Cheers, Paul. I'm mystified as to why some versions of Studio reject this file outright, and others process them differently. Out of sheer curiosity, I tried processing the file on another computer with Studio 2015 SR2 — and, as it turns out, in this test the file not only was imported, but the missing sentences do appear!

    Did you manage to get any feedback on this from the support team? As I mentioned earlier, I'd be happy to provide .SDLXLIFF files generated with 2015 SR2 and SR3 if that can be of any help. This bug is a major concern at the moment and, due to limited IT resources, it will be a while before we can migrate to 2017.
  • Many thanks for your suggestion, Naoko. It's a really clever idea and we are planning on adopting it for longer documents with footnotes where this issue has proven more likely to occur. My main concern is that it adds quite a few extra steps to our workflow, but it will tide us over until we can find a more permanent solution. Much appreciated!