I think you are right. I just focused on items before. I am sorry about that, this capitalization issue is confusing.
\nI will uncapitalize titles where needed and send the files back in batches ASAP.<\/p>\n
JM<\/p>\n
———————-<\/p>\n
Jean<\/p>\n
Let’s better wait for Alexandre’s capitalization tutorial. It is super confusing, and I am afraid to think what is in Emle’s and Carine’s files.
\nTherefore please work on proofreading new files, and when Alexandre will produce his guideline then if really any change required, only then you can make it. I will rather take more vettors to do it fast later, but we will know our files are same capitalization style.<\/p>\n
I remember when you were proofreading files<\/a> during the project, any monster names, items and any titles were not capitalized. But I really don’t know what is now.<\/p>\n ———————-<\/p>\n yes I proofread 6a and this was 2 hours.<\/p>\n ———————-<\/p>\n Ulrich, file 178 shows 97 words untranslated. Considering that originally there were 99 untranslated words to begin with, this is unacceptable. Inspection shows several English sentences and a section of German that was not marked as translated. E.g., segment 37<\/p>\n File 179 has 14 segment discrepancy caused by those segments going missing. First occurence of that is on segment 2013. To fix this, Insert blank segments until you get back to the right position. Then “Mark as Untranslated” and say yes when asked if you want to copy the source text<\/a> into the blank segments. Then translate. When done, scroll down until the next discrepancy and repeat.<\/p>\n EDIT: Fix these first before even starting on your next assignment.<\/p>\n ———————-<\/p>\n Okay. As I expected, my sickness only made the backlog worse. We haven’t started on Section 5, while I’m still encountering problem with section 3, and pretty soon I’ll run out of material from Section 2 and 4 to assign. We may get some idle time in mid-week.<\/p>\n For now though, please proofread file 162-165. Glossary at the usual place (still 09 June).<\/p>\n IMPORTANT: We discovered that overreliance on the segment filter has allowed out-of-context pretranslated and outright untranslated parts to get past the proofreaders. So first thing you should do is to look for untranslated and partially translated segments. If there’s none, then use the segment filter and proofread the translator edited parts as usual. Once you are done, note the time you tool. Now switch the filter the other way around and quickly go through the pre-translated segments. Look for out of context parts.<\/p>\n Pre-translated parts should be 95% correct, so this is should be pretty fast. When you are done write down the additional time and any comment about the accuracy of the pretranslation. We want to know this stuff how much proofreading we need to do for pretranslated materials in the future.<\/p>\n ———————-<\/p>\n Okay. As I expected, my sickness only made the backlog worse. We haven’t started on Section 5, while I’m still encountering problem with section 3, and pretty soon I’ll run out of material from Section 2 and 4 to assign. We may get some idle time in mid-week.<\/p>\n For now though, please proofread file 166-169. Glossary at the usual place (still 09 June).<\/p>\n IMPORTANT: We discovered that overreliance on the segment filter has allowed out-of-context pretranslated and outright untranslated parts to get past the proofreaders. So first thing you should do is to look for untranslated and partially translated segments. If there’s none, then use the segment filter and proofread the translator edited parts as usual. Once you are done, note the time you tool. Now switch the filter the other way around and quickly go through the pre-translated segments. Look for out of context parts.<\/p>\n Pre-translated parts should be 95% correct, so this is should be pretty fast. When you are done write down the additional time and any comment about the accuracy of the pretranslation. We want to know this stuff how much proofreading we need to do for pretranslated materials in the future.<\/p>\n ———————-<\/p>\n Okay. As I expected, my sickness only made the backlog worse. We haven’t started on Section 5, while I’m still encountering problem with section 3, and pretty soon I’ll run out of material from Section 2 and 4 to assign. We may get some idle time in mid-week.<\/p>\n For now though, please proofread file 170-173. Glossary at the usual place (still 09 June).<\/p>\n IMPORTANT: We discovered that overreliance on the segment filter has allowed out-of-context pretranslated and outright untranslated parts to get past the proofreaders. So first thing you should do is to look for untranslated and partially translated segments. If there’s none, then use the segment filter and proofread the translator edited parts as usual. Once you are done, note the time you tool. Now switch the filter the other way around and quickly go through the pre-translated segments. Look for out of context parts.<\/p>\n Pre-translated parts should be 95% correct, so this is should be pretty fast. When you are done write down the additional time and any comment about the accuracy of the pretranslation. We want to know this stuff how much proofreading we need to do for pretranslated materials in the future.<\/p>\n EDIT: incorrect file link corrected<\/p>\n ———————-<\/p>\n Okay. As I expected, my sickness only made the backlog worse. We haven’t started on Section 5, while I’m still encountering problem with section 3, and pretty soon I’ll run out of material from Section 2 and 4 to assign. We may get some idle time in mid-week.<\/p>\n For now though, please proofread file 174-177. Glossary at the usual place (still 09 June).<\/p>\n IMPORTANT: We discovered that overreliance on the segment filter has allowed out-of-context pretranslated and outright untranslated parts to get past the proofreaders. So first thing you should do is to look for untranslated and partially translated segments. If there’s none, then use the segment filter and proofread the translator edited parts as usual. Once you are done, note the time you tool. Now switch the filter the other way around and quickly go through the pre-translated segments. Look for out of context parts.<\/p>\n Pre-translated parts should be 95% correct, so this is should be pretty fast. When you are done write down the additional time and any comment about the accuracy of the pretranslation. We want to know this stuff how much proofreading we need to do for pretranslated materials in the future.<\/p>\n ———————-<\/p>\n Hi<\/p>\n I have some prior commitments – I can have this done on Wednesday (maybe earlier).<\/p>\n Cheers ———————-<\/p>\n I uploaded 14a f g j. The file name is JD – French – 14a f g j – JM” Sounds good.<\/p>\n “I was really conflicted about this but decided that there won’t be any time saved by reassigning them.<\/p>\n Do your best during the limited time, that’s all.<\/p>\n ———————-<\/p>\n I received your message after I sent the files again, I am sorry. Since the beginning of JD rescue, I have received many updates on capitalization, often contradicting each other, and consequently, I am lost, just like you. JM<\/p>\n ———————-<\/p>\n Ok, I will check both the new stuff and the untranslated parts as soon as I find the time.<\/p>\n ———————-<\/p>\n Jean<\/p>\n These are guidelines Alexandre sent few days ago, for some reason I did not receive it.<\/p>\n It is exactly same you were doing all the way before the instructions began to change – in a sentence – capitalizing only names of characters and places, standing for itself – capitalizing first word of any expression. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<\/p>\n *Character names are fully capitalized – Example: Shaw Danon, Bilu, etc.<\/p>\n *Area names are fully capitalized – Example: Incense Valley -> Vall\u00c3\u00a9e de *Item names are capitalized following this rule: The reason for this is that in a quest text, the items to find are stated English Items to find:<\/p>\n 1 Fire Sword<\/p>\n ——<\/p>\n French: Objets \u00c3 trouver :<\/p>\n 1 Ep\u00c3\u00a9e de feu<\/p>\n —–<\/p>\n Also, just to make it clear, these are not “my guidelines”, these are xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<\/p>\n ———————-<\/p>\n The last batch I uploaded follow these rules. JM<\/p>\n ———————-<\/p>\n Do you mean this one: ———————-<\/p>\n Yes, these files have taken longer than the files from JD. I had to synchronize the proper names with the glossery terms and vice versa to have reasonable consistency at least. So I had to deal more with glossary work<\/a> than usual. Sophie<\/p>\n ———————-<\/p>\n about the segment filter: I consulted with\u00a0 about the use of segment filters via telefon, but we did not work out how to use it correctly. Now I have to say I’m not even familiar with the filter function.<\/p>\n Maybe you can help me with a description about the use.<\/p>\n Sophie<\/p>\n ———————-<\/p>\n I will try to update the whole section by tomorrow morning, Europe time. I will also name them “XXX – New” to avoid confusion with the files, I updated earlier. JM<\/p>\n ———————-<\/p>\n Just confirming that I am proofreading files 8k, 15c, 15f and 15i.<\/p>\n Carine<\/p>\n ———————-<\/p>\n I sent all my hours by z_get. ———————-<\/p>\n I updated another batch for section 14. I will update the remainder of section 14 tomorrow, right now, I am too tired to work eficiently.<\/p>\n JM<\/p>\n ———————-<\/p>\n Hey<\/p>\n please find hours attached to this email.<\/p>\n ———————-<\/p>\n I uploaded the last batch of section 14.<\/p>\n JM<\/p>\n ———————-<\/p>\n
\nhttp:\/\/translationstop.com\/files\/Proofreading\/German\/02_162-165_DEU_tobe_proofed.PXF<\/p>\n
\nhttp:\/\/translationstop.com\/files\/Proofreading\/German\/02_166-169_DEU_tobe_proofed.PXF<\/p>\n
\nhttp:\/\/translationstop.com\/files\/Proofreading\/German\/02_170-173_DEU_tobe_proofed.PXF<\/p>\n
\nhttp:\/\/translationstop.com\/files\/Proofreading\/German\/02_174-177_DEU_tobe_proofed.PXF<\/p>\n
\nJan<\/p>\n
\n– Uncapitalized – New.
\nOnly place names and proper names are capitalized now. I will send the rest of section 14 during the day. Please ignore the files I uploaded before.
\nPlease let me know if everything is okay.<\/p>\n
\nI will switch back to proofreading, but without clear guidelines, I cannot be sure that capitalization will not have to be checked again, and this is probably true for every proofer.<\/p>\n
\nPlease take a look and let me know if the last file you uploaded follow this principle.<\/p>\n
\nl’Encens<\/p>\n
\n-if by themselves, we capitalize the first letter : Fire Sword -> Ep\u00c3\u00a9e
\nde feu
\n-if in the middle of a sentence, we don’t capitalize : You found a Fire
\nSword. -> Vous avez trouv\u00c3\u00a9 une \u00c3\u00a9p\u00c3\u00a9e de feu.<\/p>\n
\nagain at the end. For instance :<\/p>\n
\n—–
\nXXX asked you to find a Fire Sword in area YYY to save the villagers.<\/p>\n
\n——-
\nXXX vous a demand\u00c3\u00a9 de trouver une \u00c3\u00a9p\u00c3\u00a9e de feu dans la zone YYY pour sauver
\nles villageois.<\/p>\n
\nbasically the French language rules. This is why I have been fighting for so
\nlong to enforce them.<\/p>\n
\nCapitals for place names and proper names.
\nNo capitals for monstar names, item names, titles.
\nLet me know if you want me to proofread of to check more files for you to send to vettors.<\/p>\n
\nJD – French – 14a f g j –
\n– Uncapitalized – New.zip?
\nIf yes, then we will vet it tomorrow. If you could update some more files would be nice, but proofreading first.<\/p>\n
\nI think its only a syndrome of the beginning of the project and proofing will get much faster as the glossary is more incorporated.<\/p>\n
\nIn the meantime, I am still proofreading section 17.<\/p>\n
\nI’ll send you the ppt tomorrow showing all my files and hours.<\/p>\n