| Pages in topic: < [1 2 3 4 5 6 7] > |
| User | Thread poster: hhl Studio 2009: List of issues experienced |
|---|
Stanislav Pokorny
Czech Republic
Local time: 23:16
English to Czech
+ ...
| | Service Pack necessary | Jul 20 |
I believe that a SP improving Studio's stability should be released ASAP. I am too still experiencing a number of crashes. No loss of data, but quite an annoying thing.
I am getting more and more the impression that we are in fact working with RC 2, rather than with a mature product. Funnily enough, I didn't experience such a high number of random crashes with RC 1. 
| | | |
Saša Jovanović
Serbia
Local time: 23:16
  Member (2007)
German to Serbian
+ ...
| | Another problem with the Studio 2009 license | Jul 20 |
I bought 2 Studio 2009 plus upgrades.
I activated my SDL Trados 2007 suite licences on 2 desktop computers and 2 notebooks. (same activation code for 2 licences with 2 extra activations with the plus version)
After I activated my Studio 2009 plus licences on 2 desktop computers and 1 notebook computer, I couldn't run the activation on the second notebook computer.
I have sent a request to the SDL Trados support twice, but and I haven't received any answer so far.
[Bearbeitet am 2009-07-20 21:36 GMT]
| | | |
Myron Netchypor 
Ukraine
Local time: 00:16
 Member (2003)
English to Ukrainian
+ ...
MODERATOR | | I decided to wait for Service Pack | Jul 21 |
Agree with Eleni that it is very annoying and time consuming to translate without Insert button on-off, especially when you translate selectively between lots of tags, teminology that should be kept in sourse language, numbers, etc. This makes me switch back to SDL Trados 2007.
Eleni Zissi wrote:
I always have the source text copied to the target column and translate with Insert button on, so I can erase text while I am working (and selectively keep names or numbers, etc).
This was working properly on SDLX 2006 and SDL Trados 2007.
I also confirm number [010] (When you automatically copy the source content into the target segment if there is no TM match, the cursor always jumps to the end of these pre-translated segments.)
[10] in combination with [13] are very annoying and time consuming. |
|
| | | |
Claudia Alvis
United States
Local time: 16:16
English to Spanish
+ ...
| | Multiterm 2009 in SDLX and no-longer supported sub-languages | Jul 23 |
Will the SP have a fix for Multiterm 2009 not working in SDLX? Also, will there be work-around for those SDLX sub-languages no longer supported by Studio?
Some of us do use SDLX on a regular basis and, specially those who work in Spanish, can't work with those files in Studio because at least two Spanish sub-languages are no longer available, but can't work in SDLX either because Multiterm termbases are not recognized. Doing a language conversion is time-consuming and there's always a risk of losing important data.
| | | |
hhl
Germany
Local time: 23:16
English to German
TOPIC STARTER | | [035] "Moving" a project can cause loss of access to files | Jul 27 |
I could not find a specific "move" command or advice for moving a project & its files to another location (which is required from time to time).
So - in Projects View - I chose Project Settings > Project and changed the location entry to the desired folder. Clicking OK, the application actually moved the whole project folder content (including the prj file) to the new location, but displayed an error of access violation at the end, as the (prj) file was "used by another application".
Then trying to open the project (from the new folder, I get the error message: The selected project could not be opened.
What to do? As the old project folder still existed (including only the prj file) I tried to just copy all the project's subfolders back to the old location (folder), and then activate the Project from the old location (still in the Projects List).
But now, clicking Files View does no longer show me the files, but results in an error: Index (zero based) must be greater than or equal to zero and less than the size of the argument list. Klicking OK (the only option) results in disfigured display of the work pane and still diplays the same error message.
Confirming OK once more results in a crash of Studio.
Any idea how to get back all the files? Can you reproduce this behaviour?
This is certainly not as it should be.
  | | | |
Lutz Molderings
Germany
Local time: 23:16
Member (2007)
German to English
| | "Completed" projects become "in progress" again after restarting | Jul 29 |
Another annoying problem.
I have about 15 projects in Studio at the moment. They are all marked as completed. However, when I restart Studio one of the projects will invariably show as "in progress" again. This does not only affect one particular project, but seems to be completely random.
Of course, compared to the constant crashing (approx. every 7-8 minutes on my computer), this is only a minor problem. The constant restarting, however, really is time-consuming and annoying.
| | | |
mirekk
English to Polish
|
Having translated a Word document I tried to save it. All I got was a message "error while saving document". How can I extract my translation without saving to doc? Urgent!!!
| | | |
Myron Netchypor
Ukraine
Local time: 00:16
Member (2003)
English to Ukrainian
+ ...
MODERATOR |
[036] While translating in Full Screen (F11) Fuzzy Matches window appears just for a second and hides away, so you cannot see what is the difference between the old source from the memory and new sourse text.
| | | |
Jerzy Czopik
Germany
Local time: 23:16
Member (2003)
Polish to German
+ ...
| | Word files have always been quite tricky | Jul 29 |
Are you sure you are able to save an unprocessed original file as DOC after opening it in Studio? If yes, then you made a tag error during your translation. If not (which does not come very often with Studio) the original file is damaged and you have to repair it.
So please copy the original file to a new folder, open it again in Studio, translate the first sentence and try to save the final doc. If it works, go back to your translated text and run tag verification. If it does not work, use the "Open and repair" function in Word. If even this does not help, come back here and we will look for another solutions.
| | | |
Markus Wahlgren
Sweden
Local time: 23:16
Member (2007)
English to Swedish
| | If you can't say anything nice | Jul 29 |
The wise women called Mothers have always said "if you can't say anything nice, don't say anything at all".
That would result in an empty post from me right now.
But I am "a bit" tired of the numerous crashes. It is "mildly" annoying. Please fix it now. I am too young to have a full head of grey hair.
| | | |
Matthew Kinnersly
Japan
Local time: 07:16
Japanese to English
| | Countless random crashes with Studio 2009 | Jul 29 |
I'm now at the end of my second day of working with Studio 2009. I like how it works when it works, but I have had literally dozens of random crashes. Sometimes I get an error message, sometimes the editor stops accepting input, sometimes I get offered a bogus Abort/retry/ignore option when the only real option is "crash", and sometimes the program just freezes or vanishes. I'm not bothering to give detailed troubleshooting information, because when there are so many different modes of failure it can all be summed up as "instability", and there seems to be little point worrying about the details of individual cases. I've done the basics (applied hotfix, run utilities to clean the registry and other basic maintenance, run the application all alone after rebooting, etc). I even avoid typing too fast, as that seems to provoke it. My PC has lots of RAM, disk space and other resources. What it boils down to is that we've paid for the finished product ("innovation delivered", no less...) but we're running a Beta version with basic stability issues.
In conclusion, I think this will be a great product one day, probably around Service Pack 1 or 2, but until then, don't bother paying for a place in their troubleshooting process.
If you have already taken the plunge, note that crashes also seem to make it lose options settings, autotext entries and other useful stuff. Best to make such settings, close Studio, restart, and then keep working until the inevitable crash.
Good luck, and my thanks to all the people helping to chase down the specific issues.
| | | |
hhl
Germany
Local time: 23:16
English to German
TOPIC STARTER | | Countless random crashes ... and magic on top of it | Jul 29 |
Thank you, Matthew, for your summary.
You hit the nail on the head. I fully support your opinion. I'm working with this software for some weeks now, and it has so many great features and improvements compared to Workbench and SDLX (I'm coming from Workbench, which I had used for about 7 years, but was "forced" to use SDLX in parallel during the last 2 years), that I would not like to miss the new system.
BUT: This is really an unstable beta product, and I am already getting behind some deadlines with my jobs, due to the software's behaviour and the many errors that keep me closing and re-starting the application all day long. The latest issue today: I was wondering why I did no longer get matches in 2 translations, that I had almost completed yesterday. Strange: Selecting the whole text in the source segment and looking-up concordance delivered the 100% (even CM) match, but it was not found, when I entered the segment! Later then I did not even find the translations with concordance. Actually, the translations (at least from some of the jobs) are missing in my master TM, which is generally set for update in all projects. - This was really a shock for me, as I can deal with most other issues, hoping for a soon delivery of a service pack, but loosing parts of the TM (I have no idea what was the trigger) is not acceptable.
[Bearbeitet am 2009-07-29 22:06 GMT]
| | | |
eSDeC
Belgium
Local time: 23:16
 Partial member (2008)
German to Dutch
+ ...
| | [037] Issue with .xls files | Jul 30 |
I cannot open .xls files in Studio 2009. It says that I don't have Office 2003 installed and therefore need to save the file as .xlsx (I do have Office 2007). I have tried saving the file again as .xls in my own Excel, but that doesn't work. The workaround is simple, just save it as .xlsx and it works. But, as this software is quite expensive, it shouldn't create extra work.
Does anybody have the solution?
| | | |
Rita Fejér
Germany
Local time: 23:16
German to Hungarian
+ ...
| | More file conversion issues | Jul 30 |
I did some tests and retranslated Word and Excel files I previously translated succesful with 2007 Tag Editor. Whereas I had no problem with the conversion (final cleanup) in 2007, with Studio I was not able to convert the same translated text into the target language. Obviously both files produced by Studio were not readable: Word hung, Excel opened an empty sheet after some conversion error message. I made an experiment and took all formating out of the source Word file. Now the translated file could be converted. There seems to be a problem to handle files with a lot of formatting in it - which is why we used Tag Editor.
Also some other experience with the translated file:
- there is a format mismatch: the language specific characters (in Hungarian ő, ű, é,á..) got another format (e.g.TimesNewRoman) az the rest of the text (Arial).
- also the language formatting of the text changes from Hungarian into German and into English in between the text (which makes the spellchecker go crazy). Again a very unclean conversion!
| | | |
Matthew Kinnersly
Japan
Local time: 07:16
Japanese to English
| | Countless random crashes - I give up | Jul 30 |
Hi HHL
Thanks for the feedback. I'm in the middle of a large project with multiple PowerPoint files, so it would have been perfect to do it on the new version. I persevered longer than I should have done, until the looming prospect of a missed deadline and a flurry of six crashes inside half an hour drove me to admit defeat. So, I went back to my old Trados, did the work, made the deadline, and the next deadline, and suffered no crashes at all. Deliver us from innovation!
But seriously, can you imagine the outrage if any of us, as professional translators, delivered a piece of translation that was an error laden first draft like this piece of s**tware? Nobody would ever employ us again. And yet they delivered this under the slogan "Brand matters"!
OK, rant over. Unfortunately, Studio 2009 is going to be some undisturbed space on my hard drive until it gets some serious fixing.
| | | |
| Pages in topic: < [1 2 3 4 5 6 7] > |
Track this topic 
