I started working on my file recently, but in the first 600 words or so that I have translated so far, many terms (more than 50%) sound familiar, and many I am sure I have actually translated before.
From what you wrote above (some glossary files are still being proofread), I wonder if most of the terms I am translating here have already been translated, so my work may actually turn out to be redundant (to some degree)?
I am happy to continue translating them and being paid for them, but maybe it would make more sense to translate other, less redundant files first and see how much of this can be pretranslated once all the glossary files are ready?
I just thought you should know, and I will be happy to help with the glossary first if that would make more sense.
———————-
This is intentional.
Last project the customer complained that terms weren’t consistent, leading to a last minute nightmare as we proofread and readjust JD section 1-5, which were supposed to be done back in late February.
This was worse with the French part. The details are not relevant here, but suffice that some people get very little sleep those weeks.
For this project we want to avoid such trouble. To this end Karel wants the glossary done first, and done well, so that there will be little need for adjustment down the road.
This glossary is proofed, and when it passes proofreading, it was inserted into the Repetitions file. This repetitions file is the proofread, and when it passes proofreading it is then inserted into the regular files.
If phrases sound familiar to you, likely because for many phrases this is the third time you saw them. First during the glossary, the second during the reps, and the third, now.
This is deliberate. When your files are done it better be sparkling diamond, because they have gone under your care some three times. Proofreading ought to be a breeze too. Already we are saving resources overall because some files contains only terms and thus have no need for additional translation and proofreading.
In effect we’re putting a lot of effort into the preparation work so that down the road everything will be smoother with a higher quality result.
So check those translation for the third time. There are no “less redundant” files in this section. There are all like that.
———————-
At this point the next project is in it’s very diapers, so it will take a while. Once I will start receiving a stable flow of files, I will let you know.
” French –
Rabeyrin – 01_glossary_French – Proof: 2h45 “Sorry, but I can’t assign you a file at the moment.
Instead, please familiarise yourself with the game. Play it for a couple hours at least. Go read the wiki for the game at
http://boi-wiki.perfectworld.com/index.php/Main_Page
The glossary can be found in
http://translationstop.com/files/Glossary/
The Excel files (compressed as rar) might be helpful, just scan through it.
All hyphens are to be replaced because of conflict with Transit software. It will be reverted back to hyphens at the last step in Excel.
I don’t think we change things unnecessarily, but the client has changed his mind at least twice in the past month. This we can’t do anything about.
” French –
Rabeyrin – 02_glossary_French – Proof: 2 hours “Karel,
just uploaded the translated files 03_part_203, 204, and 205
———————-
Hi
I’m ready and available for a file assignment.
Cheers
Jan
———————-
A human error on my part erased parts of section 03. It has since been rebuild using a combination of back-ups and re-importing from the original Transit files, but one annoying thing about the fuzzyness of Transit is that a rebuild is often not quite the same as the original.
About 99% of the data are going to be the same, but that 1% difference can get annoying. It isn’t something that we can’t handle manually, but if you haven’t started far into your translation, would it be possible to let me know so I can upload a new version of the files and you can use them?
If you already finished with the whole thing, that’s alright. The 1% difference can be solved manually via fuzzy transfer.
———————-
Heiko
A human error on my part erased parts of section 03. It has since been rebuild using a combination of back-ups and re-importing from the original Transit files, but one annoying thing about the fuzzyness of Transit is that a rebuild is often not quite the same as the original.
About 99% of the data are going to be the same, but that 1% difference can get annoying. It isn’t something that we can’t handle manually, but if you haven’t started far into your translation, would it be possible to let me know so I can upload a new version of the files and you can use them?
If you already finished with the whole thing, that’s alright. The 1% difference can be solved manually via fuzzy transfer.
———————-
Please translate the following files
03_part_214, 215, 216, 219, 220, & 224.
http://translationstop.com/files/BOI/German/03_214-6_219-20_224_DEU.PXF
The last 4 files have very little untranslated parts. Some 100-200 words each. I estimate the total words to be 3500-4000. Given the low amount of words, try to get it done by Sunday. Thanks.
———————-
Sorry, I just finished translation of 03_210-13_DEU.TXF and uploaded it along with a doc file for the proofreader.
Please note that I´m available again not before today late afternoon/evening.
Heiko
———————-
Confirmed
Question:
On the last project, I got a word count with each assignment.
Will that not be the case with this project?
I like to know what I get paid when I work on something.
———————-
Hi
I have already finished part 207, and translated a big part of 209. But if it helps, I haven’t yet touched 208.
———————-
hours recorded.
———————-
Hi
I know you are still waiting for 05_Glossary to be fixed before you send it back to me, but if you have anything else for me in the meantime, I am available.
JM
———————-
Actually, carine has fixed 05_glossary. I didn’t get to it right away because I was trying to get the client’s request re: Jade Dynasty done.
However, 05_glossary_FRA is up now.
Please delete your old version and download the new one.
http://translationstop.com/files/Proofreading/French/05_glossary_FRA_tobe_proofed.PXF
That should keep you busy for a few hours while I get the client’s request done. 🙂
———————-
I uploaded a newer version of 03_part_208. Please use that instead.
http://translationstop.com/files/BOI/German/03_208_DEU.PXF
———————-
I understood that client had already replaced the sex symbols in all files. Do you still find any of these in the file you are translating now? Please let me know and I will check.
———————-
I still find these symbols, for instance in 03_part_209, segment 3243, but there are more.
For now, I left them so. I guess you can replace them automatically, later?
———————-
just at the time Karel sent his “stop translating” message, I was done with 207 and 209. For 208, I downloaded the new version, and will put that on hold now until I hear from you again.
I just uploaded the following:
03_207_and_209_Sebastian_Translated.TXF
03_207_and_209_Sebastian_Translated.doc
I just noticed that I forgot the “German” in the filename, sorry about that.
———————-
Hi
Karel just asked to stop all translations. Shall I stop proofing too?
JM
———————-
Yes, stop proofing too.
Some of the client complaints are true, but it really annoys me when he also claims that this and that are untranslated when I looked at our files and find that they are either translated in most cases and in a few cases not in our raw files at all.
Anyway, we’ll let you know if/when to continue.
———————-
Thank you for your message, here I am sending the hours report and Czech bank account number attached.
Please let me know if any question rises.
Best of the day
D.
———————-
Well, if you can get it done faster than Friday, that’ll be great too.
Anyway, if you think you can get it done faster working with the Excel files rather than Transit files, you can find the Excel files over at:
http://translationstop.com/files/Proofreading/German/
Please keep an eye over capitalisation and consistency.
Also, for the rest of section 1-5, do you think we need to look at them again for consistency issues or did you check them against the glossary when you proofed them last month?
———————-
Just to be on the safe side, the most recent dictionary of JD is German_Main__2504, isn’t it?
———————-
That’s right, 2504 is the latest glossary for Jade Dynasty.
On a slightly different topic, I actually would prefer if you do the proofreading in Excel this time. The Excel file has been aligned and vetted, and if you do it in Transit, we would have to redo those parts.
This is a preference, not a requirement.
” , has asked that you keep the 31 character limit in mind and abbreviate when necessary _and_ also give her a list of what you abbreviate and as what. This way people will abbreviate the same way throughout the files.
”
Yes it is the last one.
I would like to add to what wrote – please take care also of the 31 char abbreviation. I am attaching the two macros in one sheet you may need for that:
1. 31 char macro: Open the excel file and have it open while proofreading. Press Ctrl+Q shortcut and the macro will color all lines which contain more then 31 characters yellow.
2. In same Excel file, in cell C5 I pasted the Macro which detects number of characters in the cell on it’s left. It reacts to change in number of characters as you change it/as you type. Please paste it next to the terms which were colored yellow by the first macro, and it will help you fix it quickly and precisely.
I believe the files would also need to be spellchecked, and all yellow coloring and extra column with the second macro removed before delivery – it should be a clean file.
Please let me know if you have any questions.
Permalink //
If you want to be a writer, I hhgily encourage you to give it a try! My most important advice is to remember that writing is a BUSINESS, and you have to be professional and entrepreneurial at all times. And, keep learning how to write better. That usually means edit, edit, EDIT your little behind off.How much writers make depends on their experience, not necessarily their education. These freelance writing pay rates aren’t set in stone; it’s different for each writer.