![]() Did that, converted back to sdlproj, opened it in Studio. I decided to dump the entire section (about five lines) and fix the end of the xml file, where some end tags appeared to be missing. I could change it, but into what? If I knew that we'd have a simple fix. The first error message I had, referred to exactly this Guid format being wrong. Line 15861 looks like this:Īs even I can see this part looks totally wrong:įileVersion Guid="edb56bc2-9b28-48b2-9c2ENLAPTOP\RIEN LAPTOP" Then I opened it in Notepad++ (free download). I renamed a copy of the project file (sdlproj) into the same file name, but with an xml suffix. Until that happens: SDL Studio NOT recommended for anyone below the level of computer expert! Shouldn't it be designed to keep THEIR needs in mind? Wake up, SDL! You are selling this hypersensitive tool suite at a profit to thousands of not-so-computer-savvy translators. Thanks, guys! Even so, how much geekdom is required to be an SDL Studio user? Will several years of technical studies do, or is a degree in software engineering a requirement? Which is reassuring, especially because they are computer geeks, so they found a workaround. Looking through the posts on the subject in this forum I see that this has happened to some of my colleagues before. ![]() One little error in an XML file, it could happen any time, out of the blue and through nobody's doing and your project is toast! Today I found out that the system isn't even close to foolproof. This time they took the over-the-top, convoluted approach: a jungle of non-editable Project and Main Memories that are somewhere hidden on your hard disk, but where? Still, that wouldn't be so bad, if it worked RELIABLY. It would have been so simple to add an integrated backup solution (see the competition), but the program designers just couldn't be bothered. Trados up until Studio too easily messed things up and your TM could be irretrievably lost just like that (which is still the case with any version of Trados, by the way, so if you haven't switched to Studio: backup, backup, backup your TMs). There is no alternative, there is no backup, there is no safety net.įor years users have been complaining that the one big SDL policy error is their total disregard for data safety. A built-in SDL Studio error! It made an error in ONE XML file and now the ENTIRE half-finished 80.000 word project cannot be opened. Not an error of mine, Windows, or the power grid. Error message: "Failed to load project from. This day was bound to come, wasn't it: SDL Studio will not open my current 8000 Euro project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |