I’m not sure why the error messages show up because I did nothing different with the 2 June dictionary compared to 28 May dictionary.
Next time you could try deleting the older dictionary prior to accepting the new one, but I am actually puzzled as to the root cause of the error message, so I don’t know whether that will work.
Don’t worry about it overwriting 207, 209, or the Names etc.
For 207 and 209 as long as you keep a back-up of the finished files that’s good enough for me. For your suggested new project to send with the dictionary, the Names etc. is the new project. Now that the glossary is complete the Names project is obsolete. Since its size is small, I just attached the dictionary to it.
As for the error in the dictionary, send your comment with specific examples to . He’s the lead translator for BoI and while I am concerned about glossary, I am not competent in German to judge either the current glossary or your comment.
I just want to let you know that IÂ´ll be available again for translation/proofing from upcoming Sunday afternoon on.
Thank you for the update. Are you in charge of allocating files for this project?
I should be done with section 14 today. I was planning on asking Alexandre which section he wanted me to tackle next, but if you are in charge, it is up to you.
Once I am done with section 14, I will post the proofreading hours and upload the reports.
Alexandre and I decided not to send the files yet, because they will probably need to be polished as we go.
Please let me know if you have questions or comments.
I keep receiving instructions from Karel, but I am not sure if I am supposed to do anything. Please let me know, I will now be available on Sunday, Monday, Tuesday and Wednesday.
I have finished proofreading file 7f. I am uploading it as well as the word document that specifies the time I spent on it and the main changes I made (mostly shortening). I also highlighted two issues I couldn’t resolve with the help of the glossary (regarding shortening and order of words). If Alexandre or
could have a look at it, I can then make the changes if needed and upload the file again.
is working on BOI, and he is the one who concentrates the terminology proposals. You can contact him with this on CS. It will be better if you do it then me, because he may have some questions to you about these terms.
Thank you for the update. I think if we are trying to fix terminology consistency, some of the most important sections are 1-6. Please begin with sections 1 and 2, particularly files which were proofread by . I expect there significant issues. I also expect they may need to be abbreviated, therefore please find attached 31 char macro.
To activate it, have the attached sheet open while working on your file and press CTRL+Q shortcut. It will color all lines with more then 31 chars yellow. Additionally, in the same sheet I pasted another macro (in a blue cell). This macro detects number of chars in a cell on it’s left, and reacts to any changes you make to the cell. Very convenient for abbreviation. Just paste it in the right of the cells which colored yellow.
Please let me know if you have any questions.
You made my day with this macro! Thanks a lot. If it’s not already done, you might want to send it to Carine, she told me she had issues with section 7, so this would be very helpful if character limitation applies to her section.
I will start with section 1 as soon as I am done with section 14 – probably tonight, US time.
yes, 04_reps_DEU was short. I will upload it in a minute (as always, with comments on the glossary for ), and will be ready for a next file tomorrow.
When working on files that have already been proofread, should I write a report on the proofreader or should I not write any report?
Please take for proofreading files 15s-u. The files in Excel format can be downloaded form translators files server. Please proofread, paying particular attention to terminology consistency with the up-to date glossary (http://translationstop.com/files/FTP/French_Glossary_14May.xls) and spellcheck. As to capitalization, please apply the new rules (first letter of first word of special terms) in case you make changes to the word, but if the term is fine, don’t change it.
Sebastian has several suggestions regarding the glossary.
Please decide what to incorporate into the glossary and let me know when there’s an update.
There’s also a couple files that need proofreading. You have said that Sophie’s available for proofreading, but please ask her to register to Open Ticket and post something so we know that she has registered.
I will incorporate into the dictionary as soon as I get the chance. Sophie will not be available for proofreading until tomorrow night or Saturday, I’m afraid, but I will brief her on the procedure.
Ulrich, I need confirmation on whether you can work on 05_reps_DEU and finish it within the timeframe.
Karel said he sent you payment some time ago, but go ahead and check it yourself.
Gah, too tired to think.
Okay, regardless of whether you are available or not, don’t start work on 05_reps until I tell you so.
Let me know whether you’re available first and wait for a confirmation first.
I’m trying to make an alternative plan in case you aren’t available. This may require me to assign 05_reps to someone else. Yet since it’s quite late at night, I’m finding that I’m not thinking clearly. So I’m asking you to wait for a bit and to let me know your availability first.
Ok, I had to wait for the money first. Now it’s arrived and I am ready to work again.
Ca. 550 words should normally be possible in two days. I will check tomorrow to make sure there are no unexpected difficulties. I don’t work on Sundays, though. Will get back to you tomorrow.
Here is the hour count for section 14.
Still waiting for regarding glossary.
But proofreading must go on, so please proofread ‘s 203-205.
the client wants to see the German glossary tonight (their morning).
I can give them the 02 June version, but if you can look through Sebastian’s suggestions and incorporate what needs to be incorporated, that will be great.
Aren’t you busy with JD.repair?
When you are finally done with JD, let me know again.
I’ll finish my JD.repair work this morning. So I will be available to translate BOI files from this afternoon and during the weekend.
I prefer if you write your proofreading hours directly in the body of the message here on OT, it allows me to update GS directly from my e-mail. Sorry if instructions on this issue were confusing.
I will request Alexandre or
to take a look at your file.
I believe you still have 2 files left, when do you think you will be able to complete them?
Are you ready to continue working on JD for few more days? There are quite lot of files there, and I have only you and working on this project.
Please let me know.
I will start proofreading now.
Should I check the segments as “checked 1” or anything while proofreading?
For some reason, yesterday I forgot to write that I had to leave many(!) strings untranslated, because they were in chinese (much more than usual). Sorry about that.
Whatever we can do – all improves our final result, which, in my opinion wasn’t bad since the beginning. May I know which files required polishing?
Did you make the abbreviation work on them?
My general idea is to proofread files 1. translated by weaker translators 2. To proofread files translated and proofread by same translator. Good as one may be, but we don’t see our own mistakes.
So I guess next files for you to work on would be section 16. Please pick and proofread several files form the section – though it had been proofread, I think it may require additional look. I suggest to begin with files 16 a-f, and then if you will have time to continue to files 16j-m.
Let me know what you think.
The position had been filled at the moment, but in case it may reopen again, I will keep your applications in mind.
I think the overall quality of the files is good. What I found in 6c and 6d were mainly deviations from the glossary ranging from slight to absolute deviations and some mistranslated words such as mount, skysong or Inc. valley.
This might be partly due to some inconsistencies in the glossary file but some segments were just not checked against the glossary file.
As for abbreviations, I have the 31-macro running all the time to make sure that this won’t become an issue again.
I’ll do my best to fix these issues but it is rather time-consuming.