Hi Thomas, Le 12/10/2013 19:59, Thomas Hackert a écrit : > Hello Sophie, *, > sorry for being such a pest, but ... ;) > > On Freitag, 11. Oktober 2013 09:17 Sophie wrote: >> I've written two guides to help new comers with their >> localization: > <snip> >> - one about UI and Help files contents (variables, xml) and some >> grep/sed commands >> > https://wiki.documentfoundation.org/UI_and_Help_files_Content_Guide >> >> If you see something missing or not clear enough, don't hesitate >> to tell me. > > After proofreading I still have a couple of questions and or > annotations, so be prepared ... ;) tl;dr ... ;) > > 1. You have really often used "must not". I have changed some of > them to "have not to", "need not" or tried to circumvent them > otherwise ... ;) But there are still a lot of them in the text, so > it would be nice, if someone has another look at it ... ;) > I am not sure (my last English lesson is too far in the past, > sorry), but was it not mostly used in official texts, legal > instruments and the like?
I used 'must not' because it's a 'must not' :) > > 2. Below "3.3 <bookmark_value></bookmark_value>" you wrote > <quote> > Sometimes it happens that the word in the sources has a different > meaning in English but not in your language, like header and title. > If you find such entry like > <bookmark_value>Header;Title</bookmark_value>, you can just remove > it from your translation, as it will have no effect. > </quote> > (first point below the grey box). Are you sure, that you really can > remove it? I seem to remember, that either Pootle will spit out an > error message or there will be a problem during compiling LO (but I > may be wrong here ... ;) ). Yes, I'm sure, I've already done it (and already broke the index too ;) > > 3. There is also the following: > <quote> > There should not be two similar entries in the help directory > because it will break the index display in the help UI. > </quote> > . Should it not be > <quote> > There should not be the same entry more than one time in the help > directory because it will break the index display in the help UI. > </quote> > or > <quote> > There should not more than one entry with the same name in the help > directory because it will break the index display in the help UI. > </quote> > (or something like that ... ;) ) instead? For me it means the same, but if you prefer one over another, please change it. Your last proposition however could be difficult to understand, because 'name' is less precise. > > 4. Below "4.1 Translate Toolkit" you wrote the program names > capitalized. Was it intended? If so, you need to change it back, as > I have used their spelling, like they appear in the command line ... > ;) no problem :) > > 5. Same paragraph: Just out of interest: Why do you link to > Translate Toolkit's online documentation? Would it not be more > helpful to mention "man poterminoloy" or "info poterminology" and > the like? I did so because most of the translators are not technical at all and will prefer to read the help on a web page than on a terminal > > 6. Thank you for "4.2 Using grep to find strings" :) Some really > interesting information in it, nice :) But why do you write every > option separatly? Like > <quote> > grep -r -i 'word' directory > </quote> > ? You could also use > <quote> > grep -ri 'word' directory > </quote> > without any problem (or better say: /I/ can use it with grep 2.14 > under Debian Testing AMD64) ... ;) The same applies to > <quote> > grep -r -i -n 'word' directory > </quote> > , which you can shorten to > <quote> > grep -rin 'word' directory > </quote> > ... ;) same as above, I prefer they really understand what they do, so step by step with one option separated from the others, when you learn, it is easier to execute and remember. I could have given only one command line with all the parameters explained below, but when it's your first try, it is safe to do one thing after another. > > 7. Same place: > <quote> > If you have an escaping character in your search, like an apostrophe > (e.g. child's book in English or l'objet in French), the simplest > way to overcome that is to enclose the word to search with double > quotes instead of single ones, like in this example: > </quote> > What do you mean with "escaping character" here? Did you not mean > "characters to escape"? I mean an apostrophe, like I mentioned it, it is an escaping character that will be interpreted when you don't want it. > > 8. The last sentence from "4.3 Using sed to modify your files": > <quote> > you will find more information on the gnu site about the delimiters, > the regular expressions and syntax. > </quote> > . Why do you link to the online version of the manpage from sed, > when it is installed on your system ;? And you could use "info sed" > as well to get additional information ... ;) same as above. My position here is to help people who have never touched a terminal and they will feel more at ease reading out of it. > > 9. Some of the text of the grey boxes with the examples are too > long, when I view them with FF 27.0a1 (2013-10-12) under Debian > Testing AMD64 and using a display resolution of 1024x768 (like the > box with > <quote> > #1 Verify Impress is running \n > #2 For Bluetooth user, enable "Preferences"-"LibreOffice > Impress"-"General"-"Enable remote control"\n > #3 For WiFi user, tick > "Preferences"-"LibreOffice"-"Advanced"-"Enable Experimental > Features" \n > </quote> > , where the last part of the second line (l"\n") is outside of the > box ... :( Is there a possibility to get the texts inside the grey > box (either resizing the box or splitting the lines or ...)? the box get the size of the sentence, so I'll split the sentence in more lines. > > That was all, I have found so far ... ;) Have a nice evening > Thomas. Thanks a lot for your proof reading and suggestions :) Kind regards Sophie -- Sophie Gautier <sophie.gaut...@documentfoundation.org> Tel:+33683901545 Membership & Certification Committee Member - Co-founder The Document Foundation -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
