I need your advice again.
There are quatation marks in some files. Sometimes they are present both in the sourse and target text, sometimes -only in the source.
I need to estimate, whether such discrepancy is acceptable or it would look bad if some of the windows
were inconsistent in this way.
I attach 2 files as an example.
Please, take a look at them in your EARLIEST convenience.
———————-
I need your advice.
There are quatation marks in some files. Sometimes they are present both in the sourse and target text, sometimes -only in the source.
I need to estimate, whether such discrepancy is acceptable or it would look bad if some of the windows
were inconsistent in this way.
I attach 2 files as an example.
Please, take a look at them in your EARLIEST convenience.
———————-
Just uploaded 05_257.
———————-
First I have to say that Karel has sent out a mail with project instructions at the end of May. There he told us:
“Do not use quotes in quest text. All kinds of quotes and quotation marks often cause the text to not display correctly. Since it’s hard to tell when it’s a quest text and when not, please always try to avoid them.”
So I did.
Today he stated:
“Try NOT to use double quotations marks ( ” ) but single ( ‘ ) are okay. However, in certain cells ” is okay, so if they are used in the source English cell, you can also use them in the target cell.”
So, I´ve ever tried to avoid any quotation marks and I also did when proofing.
Regarding your files:
In file 02_part_164 I´ve inserted the double quotation marks in all four lines because they´re referring to titles.
In file 02_part_165 I´ve inserted the double quotation marks in lines 315 and 623 for the same reason BUT the single quotation mark in line 255 refers to a possessive Noun.
In contrast to English the German don´t need a single quotation mark for proper names that doesn´t end with an “s”. If they end with an “s”, they also need a single quotation mark.
Example:
Apollo´s sword – Apollos Schwert
Hades´s sword – Hades´ Schwert
In the end, when the source text contains double quotation marks we should also use them.
I hope this will help you.
Best
———————-
Ulrich
Vetting is a separate process, when people comparing translation to the source text. We compare the text, watch for some spaces issues, some punctuation and so on.
But we will talk today about “pluses issue”.
If we find pluses in the target, but not in the source, we should give file back to check, because pluses are left by translator on purpose.
Could you please resolve these issues for us?
You will familiarize yourself better with vetting process after you check the file 02_178.
File and comments attached.
Please write me back if you have any questions.
———————-
Ok, received. I will get back to you about this later. At the moment I need to concentrate on the file I’m working on.
———————-
I attach more files to check for the same issue. There is a Word file in the zip, where you can find the list of the segments to check. Please, add quatation marks if you consider it would be right.
Please, do it ASAP.
———————-
Ulrich
I am very much sorry for interrupting your work.
But we do need 178 ASAP.
Please, do us a favor.
———————-
I´ve inserted the quotation marks.
———————-
!!
———————-
Would you like to proofread file 02_194?
http://translationstop.com/files/Proofreading/German/02_194_DEU_tobe_proofed.PXF
Please confirm
———————-
Ok. But I can’t find the passages listed in the word file “Ales comments”. In my version of Transit, I only have “segments”, not “lines”.
It is obviously mainly about “+” in my translation. Please note that I (sparingly) put these where I’m not 100 % sure if my translation of a word / phrase fits and would like someone else to revise the passage. So I’m afraid I won’t be able to help much on these.
Is Ale the lead translator with this project?
———————-
Maybe it’s good to inform you that Transit just crashed (shut down) within half a minute of relaunching.
———————-
I confirm proofing file 02_194.
Please note that I´ll be unavailable from tomorrow Wednesday afternoon till Thursday noon.
———————-
Ulrich
No, Ales is a vettor.
We will take care of 178 file.
Sorry, about Transit. I will let know about this.
———————-
Thank you for letting us know.
Is it possible to ask you for a favor ASAP?
Please resolve pluses and 1 hyphen issue.
File 178 is attached.
” What’s happening Uli? Worked for you on the last project, no? And no one has had problems so far.
”
Issues solved. I´ve also seen some translation issues but according to the accounting_web site it wasn´t proofed yet.
———————-
Thanks for looking after the 178 file.
There are no bigger problems with Transit in general. I just thought I’d let you know for your general reliability statistics regarding the program.
Uli” I’m looking into other options but it will take time to test and make sure it works. For now I know Transit well. But hopefully things will improve as we move forward.
”
Thank you very much.
File was not proofread, that is correct.
It was pre-translated mostly.
We believe it is an old Glossary issues.
What is your opinion, can we leave it?
———————-
Ulrich
we will note that.
———————-
Regarding your .hhh. error, that has been taken care of. Please be more careful in the future.
If there’s a quote in the original English, keep them in the German. It’s only when the quote is in the Quest text that the client’s software has trouble.
———————-
It´s a repetetive file and I just found very few issues at the end of file and changed very few terms, maybe around ten. Please find the edited file attached.
———————-
I additionally want to ask you please to do proofread mostly for translator’s part, not so much for pre-translated.
———————-
Yes, I´ll think of that when proofing.
———————-
in my opinion, we should follow the source here. So if the source has quotation marks, the target should have them, too.
Sophie
———————-
We will use CAT. There’s no choice about it. It’s the only way we can keep a project of this scale organized enough while still remaining economical. No, really, we understand where you are coming from, and if this is a small subbing project with only one or two translators, we’d ditch Transit. But a 1.5 million words project needs some sort of CAT.
If you have a suggestion on which CAT program to use, we will consider it, although obviously we can’t change mid-project.
First, let’s make sure you have downloaded the glossary. Transit calls this a “dictionary”. Well, in a sense they’re right, but who cares what the name is, right?
Glossaries are always uploaded to this site:
http://translationstop.com/files/Glossary/
Download the Glossary_DEU_21Jun.PXF. Accept everything. The Names_Files_etc is just a “carrier” file and you can ignore it afterward, but the dictionary is attached to it.
If for some reason you want the Excel version, just look for the zip file in the same directory. They contain mostly the same stuff. There are some additional markings in the Excel file, but they’re irrelevant for you.
Okay so you have the dictionary somewhere. Now open the project file you’re assigned. No dictionary. This is because Transit has not associated the dictionary file with your current project. So let’s do this.
Go to Project -> Settings. You’ll get a window with many tabs. Click on the TermStar Dictionaries tab. Right now your Current Dictionary field should be empty. Same with Dictionaries Within Project field.
Click on Add. You should see Video.German_MAIN. Add that in.
When you are done, click OK, then Apply, then OK. Again. Now Transit has associated the dictionary with your project. If you want to de-associate the dictionary, use a similar procedure. When there’s a new update and you want to delete the old dictionary, you go to Options -> Database Administrator -> Expert and then find the dictionary and Delete it. Then you can download the new glossary/dictionary and repeat the process I described earlier.
Now that you have a dictionary, you can click on a word and then click on Find In Dictionary (second row of icons on top, 6th from right) and it will open the dictionary on the relevant entry (or close to it). You may need to use page-up and page-down to scroll up and down.
We use the glossary/dictionary so that a term is always translated the same way. Often the same term can be translated 6-7 different ways without changing the meaning. For a computer game, this is bad. Hence the glossary.
Hope this helps.