| Pages in topic: [1 2] > |
Problem with saving virtually merged files in editor Thread poster: Alaa Zeineldine
|
|---|
Alaa Zeineldine 
Egypt
Local time: 23:32
Member (2002)
English to Arabic
+ ...
Trados Studio 2022 R2 and earlier versions.
While editing virtually merged files in the Editor, attempts to save (Ctrl+s) cause the error "Argument '0' is out of range. It should be between 1 and 2147483647. Parameter name: ChildFileDocuments.Count". There does not seem to be a way to get around this error. The only option is to open each file individually, which defeats the purpose of virtually merging files.
There is a knowledge base entry for this problem (KB0036830) that is four years old, but it does not provide any additional help over what I mentioned above.
I wonder if anyone has come up with a solution for this problem, or a real workaround that allows one to edit the merged files and save them.
[Edited at 2025-05-09 23:22 GMT]
| | | |
| |
Alaa Zeineldine
Egypt
Local time: 23:32
Member (2002)
English to Arabic
+ ...
TOPIC STARTER | Merged files should be saved to their individual files | May 9 |
Gjorgji Apostolovski wrote:
...
As far I as understood, you can merge those files only if you open and put them in a new project. You can't merge them as one file into target.
Thank you for your answer, but I am not trying to save the merged files into a single target file. The way this is supposed to work is that when you try to save merged files in the editor, you actually save the individual files, but this is not working now.
The KB acknowledges this is a Studio defect:
https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0036830
[Edited at 2025-05-09 23:59 GMT]
| | | |
| so there's a solution on that link | May 10 |
Alaa Zeineldine wrote:
Gjorgji Apostolovski wrote:
...
As far I as understood, you can merge those files only if you open and put them in a new project. You can't merge them as one file into target.
Thank you for your answer, but I am not trying to save the merged files into a single target file. The way this is supposed to work is that when you try to save merged files in the editor, you actually save the individual files, but this is not working now.
The KB acknowledges this is a Studio defect:
https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0036830[Edited at 2025-05-09 23:59 GMT]
So it says open them one by one in the Editor.
And when you finish editing them one by one in the Editor, and saving them one by one, then can you open and merge them into a new project as a final edited file?
| | |
|
|
|
Alaa Zeineldine
Egypt
Local time: 23:32
Member (2002)
English to Arabic
+ ...
TOPIC STARTER | Informed answers please | May 10 |
Gjorgji Apostolovski wrote:
So it says open them one by one in the Editor.
And when you finish editing them one by one in the Editor, and saving them one by one, then can you open and merge them into a new project as a final edited file?
Dear Gjorgji,
You do not seem to be informed about the concepts or functionalities involved here because you are not a Trados user, and probably not a CAT tool user in general. But thanks for trying to help.
[Edited at 2025-05-10 20:38 GMT]
| | | |
| Post removed: This post was hidden by a moderator or staff member because it was not in line with site rule |
Stepan Konev
Russian Federation
Local time: 23:32
English to Russian
Can you please elaborate on what you mean by the "virtually merged files"?
Do you have (1) multiple individual source files like docx, etc. converted into multiple individual sdlxliff files which you then open for translation in a multiple files mode in the Editor, or (2) is it originally one or more single master sdlxliff files obtained by your client from merging other multiple files?
I am asking to make sure that you understand the difference between virtually (scenario 1 above) ... See more Can you please elaborate on what you mean by the "virtually merged files"?
Do you have (1) multiple individual source files like docx, etc. converted into multiple individual sdlxliff files which you then open for translation in a multiple files mode in the Editor, or (2) is it originally one or more single master sdlxliff files obtained by your client from merging other multiple files?
I am asking to make sure that you understand the difference between virtually (scenario 1 above) and physically (scenario 2 above) merged files.
The error you refer to usually occurs when you edit physically merged sdlxliff files that you attempt to virtually merge then again. With this scenario, you end up with double merging: physical first and then virtual. This causes the error. If this is your case, ask your client to give you the individual files as they existed before they physically merged them.
[Edited at 2025-05-11 01:08 GMT] ▲ Collapse
| | | |
Alaa Zeineldine
Egypt
Local time: 23:32
Member (2002)
English to Arabic
+ ...
TOPIC STARTER
Gjorgji Apostolovski wrote:
....
You have made an unacceptable accusation that I have reported to site moderators. Apart from that, I will not respond further to any unhelpful comments.
| | |
|
|
|
Alaa Zeineldine
Egypt
Local time: 23:32
Member (2002)
English to Arabic
+ ...
TOPIC STARTER
Stepan Konev wrote:
Can you please elaborate on what you mean by the "virtually merged files"?
Do you have (1) multiple individual source files like docx, etc. converted into multiple individual sdlxliff files which you then open for translation in a multiple files mode in the Editor, or (2) is it originally one or more single master sdlxliff files obtained by your client from merging other multiple files?
I am asking to make sure that you understand the difference between virtually (scenario 1 above) and physically (scenario 2 above) merged files.
The error you refer to usually occurs when you edit physically merged sdlxliff files that you attempt to virtually merge then again. With this scenario, you end up with double merging: physical first and then virtual. This causes the error. If this is your case, ask your client to give you the individual files as they existed before they physically merged them.
[Edited at 2025-05-11 01:08 GMT]
Hello Stepan,
It is Scenario (2). The client usually sends a package that, in this case, contains two individual sdlxliff files made by merging many small xml files. I select both sdlxliff files and open them for translation.
As I mentioned at the top of this thread, the error has been there for several years and is acknowledged by RWS. I am hoping perhaps someone has found a work-around to avoid editing each file individually.
Thanks for your help.
| | | |
Stepan Konev
Russian Federation
Local time: 23:32
English to Russian
| Translate 1, pretranslate 2 | May 11 |
Alaa Zeineldine wrote:
The client usually sends a package that, in this case, contains two individual sdlxliff files made by merging many small xml files. I select both sdlxliff files and open them for translation. This is exactly the culprit. I see your point now. You hope that someone has found a workaround over the past 9 years since the issue was first reported. I don't know how to do that, but probably you can translate File 1 first and once you are done with it, pretranslate File 2 against your File 1 translation.
| | | |
| Post removed: This post was hidden by a moderator or staff member for the following reason: Violation of rule https://www.proz.com/siterules/general/2#2 |
expressisverbis
Portugal
Local time: 21:32
Member (2015)
English to Portuguese
+ ...
| Trados Live or GroupShare, if you are working in a team environment | May 11 |
You are right.
This is a long-standing and frustrating bug in Trados Studio 2022 R2 and earlier among the well-known "unsigned Trados Studio plug-in found" message every time I open Trados...
Upgrading to Trados Studio 2024 has improved file merging stability (sometimes I think these bugs are "made" to motivate users to upgrade their versions), or using Trados Live Team or GroupShare where file merging behaves more predictably.
| | |
|
|
|
Alaa Zeineldine
Egypt
Local time: 23:32
Member (2002)
English to Arabic
+ ...
TOPIC STARTER | Translate pretranslate | May 11 |
Stepan Konev wrote:
... probably you can translate File 1 first and once you are done with it, pretranslate File 2 against your File 1 translation.
Thanks Stepan,
That is the next best option. It is close to what I have been doing, except I translate one file, then translate the other file against the TM updated from the first translation. Probably pre-translating the second file is more efficient. Not being able to merge the files for editing is a more serious problem.
| | | |
Stepan Konev
Russian Federation
Local time: 23:32
English to Russian
expressisverbis wrote:
This is a long-standing and frustrating bug in Trados Studio 2022 R2 and earlier among the well-known "unsigned Trados Studio plug-in found" message every time I open Trados... Actually the above referenced issue is not about plug-ins. This is just a rare scenario involving double merging that Trados never supported or was not designed for.
What regards the unsigned plug-in message, you can fix it by removing the problem plug-in if you don't use it. As far as I remember the unsigned status means the plug-in has not been approved by RWS yet.
| | | |
Alaa Zeineldine
Egypt
Local time: 23:32
Member (2002)
English to Arabic
+ ...
TOPIC STARTER
expressisverbis wrote:
Upgrading to Trados Studio 2024 has improved file merging stability (sometimes I think these bugs are "made" to motivate users to upgrade their versions), or using Trados Live Team or GroupShare where file merging behaves more predictably.
Thanks for this info. In fact, my Trados 2022 license included the right to install Trados 2024 when it's available. I have been delaying this step to avoid any side effects from switching releases. Maybe I should bite the bullet and upgrade then.
| | | |
| Pages in topic: [1 2] > |
Login to reply/comment 
Translation news related to SDL Trados
