Go Rinse! You're a proofreading machine! ># : kcookiespolicies.cpp:133 >Change the policy selected item in the list box.
Fixed >#: tips.cc:165 >"priviledges" should be "privileges" (?) Fixed >Yep, me again :) > >I found these strings in kcmstyle.po: > ># : kcmstyle.cpp:338 >This module has detected that the currently selected style ( >#: kcmstyle.cpp:339 >) geen Menu Translucency ondersteundt, daarom is dit menu-effect >uitgeschakeld. Could someone knowledgeable about i18n() take a look at this? I think the formatting in the string is breaking the macro. >This string is missing a period at the end of the last sentence: > >#: kproxyexceptiondlg.cpp:87 . . >this is by the way a very common error in the strings. should I report every >instance I find, or leave it up to the English proofreaders? Yes, that's a very common issue. At a minimum, apps and documentation should be internally consistent. We'd like to establish a standard, but in the meantime don't bother reporting them. >i'm probably being picky, but what is the \n doing in this string? > >#: rc.cpp:11 >Enter your full name here, e.g. \"John Doe\" (without the quotation\n >marks). Some people like to provide a nick name only. You can leave this >field blank and still use email. However, providing your full name is ><em>recommended</em> as this makes it much easier for your recipient to >browse his or her email. Reading it in Designer, it looks OK. I made "nickname" one word, though. >in kdat.po I found this string: > >#: ErrorHandler.cpp:51 > caught.\n >Exit the program from File->Quit or do \"kill -9 <pid>\" if you like.\n > >What comes in front of "caught"? It's putting an error code in front of that string. >Then I found these strings: > >#: Tape.cpp:380 >Error during fseek #1 while accessing archive \": >#: Tape.cpp:393 >Error while accessing string #1 in archive \": ># : Tape.cpp:406 >Error while accessing string #2 in archive \": >#: Tape.cpp:419 >Error during fseek #2 while accessing archive \": These shouldn't appear in non-debugging code, if I understand it correctly, so maybe you don't need to translate it. Whether that has anything to do with the slash I don't know.
