Re: [libreoffice-documentation] Re: Use of "allow to" in documentation
Tom,
Steve's idea is a good one, but who is the "you". In a help file it's fairly
obvious - the person getting help. In an API definition it's not so obvious. Is
it the programmer or the program user?
I take the issue you raise about translation. I'm a newbie in LO documentation
(apart from using it, that is), and don't know the processes. For the help
files it may not be too much of a problem as I think there are only 8 which use
"allow to". But it's everywhere in the API documentation - that would be a
major task. I won't take any action until I hear back from you.
There's a discussion here about a style guide - while grammatical issues may
not be strictly "style" common mistranslations could well be pointed out there.
Another issue is that some documents don't use articles ("a", "the") very well,
Presumably a translation issue. Easy to do it your first language isn't the
target language and in some cases even if it is.
Best regards,
Peter
mailto:l...@ptoye.com
www.ptoye.com
-
Sunday, December 6, 2015, 9:06:06 PM, you wrote:
> Hi :)
> I really like Steve Edmonds' suggestion as a quick fix to quickly
> solve the immediate issue through tons of the documentation in one
> fast process. Alex Thurgoodes' and Peter Toyes' ideas may be higher
> quality in many cases but i think they require a more in-depth reading
> and understanding of each occurrence. Using Steve's suggestion as a
> "first parse" and then following up with the more intensive ideas
> might just be completely perfect.
> I do have 1 worry wrt the help files. These files get translated and
> changes such as are being proposed here would mark all those
> translations as wrong. For teams with a lot of people or where they
> have completed translating all the help-files, or done none at all,
> there is less of a problem. However my worry for teams who have done
> a significant amount of work but not yet completed all the help files.
> For them it will mean a significant amount of work to re-check work
> they have already done in order to find where they really need to
> start from.
> So, i will email the international translators team to let them know
> what is being planned and to ask their advice. Until we get feedback
> from them please can i ask that wide-scale correction of the
> help-files gets delayed? Sorry i am really late in this thread! So
> if it's already been done then don't worry and just let me know
> because it's my fault for not noticing this thread earlier.
> I think the help files need a lot of work, both in
> 1. reviewing how the functionality really works and checking the
> accuracy of the instructions and
> 2. proof-reading grammar and such like to make it a bit less geeky
> and more "man(/woman) on the street"
> As they are those help-files are much easier to translate and a LOT of
> good work is done by a tiny team. However i think it would still be
> good if native-English speakers could re-phrase some of it or/and
> simplify it.
> Good luck with the Wiki! It is really great to see this type of work
> getting under-way. Regardless of my earlier misgivings about the
> help-files i think this is all something that would be great to see
> being done and it would help LibreOffice quite a lot to get this sort
> of thing under-way.
> Many thanks and regards from
> Tom :)
> On 6 December 2015 at 14:56, ptoye <l...@ptoye.com> wrote:
>> Hi Jan,
>>
>> I read through the pages on gerrit setup (two of them - they seem to be very
>> similar to start with, and I fond that bit confusing!), and started to get
>> onto the gerrit system. Then I found that the commands to use gerrit were
>> totally Unix-oriented so asked on IRC and was pointed to the LO development
>> on Windows wiki page, which implies that I have to install cygwin. Is this
>> necessary just for gerrit registration? I won't be building LO itself, just
>> editing the help files.
>>
>> Best regards,
>>
>> Peter
>> mailto:l...@ptoye.com
>> www.ptoye.com
>>
>> -
>> Thursday, December 3, 2015, 8:12:47 PM, you wrote:
>>
>>
>> Hi Peter,
>>
>> Peter Toye píše v St 02. 12. 2015 v 16:13 +:
>>
>>> OK, when I have time I'll fix the wiki, That's the easy bit.
>>
>> Cool, thanks! :-)
>>
>>> For the help files, I already have a Git system on my PC (used with
>>> Visual Studio Express), but don't know Gerrit at all. I'll read
>>> through the documentation on how Git is used for the help files, but I
>>> think I'll need help on Gerrit. It won't be for a few days.
>>
>> I see. ge
Re: [libreoffice-documentation] Use of "allow to" in documentation
Jan, OK, when I have time I'll fix the wiki, That's the easy bit. For the help files, I already have a Git system on my PC (used with Visual Studio Express), but don't know Gerrit at all. I'll read through the documentation on how Git is used for the help files, but I think I'll need help on Gerrit. It won't be for a few days. I don't have an IRC client (or does WIndows 7 have one built-in - I've not found it?) so that will be the first thing. What timezone are you in - your name implies the Central European time zone - UTC+1, so it shouldn't be too difficult to find a time that we're both awake. Best regards, Peter mailto:l...@ptoye.com www.ptoye.com - Wednesday, December 2, 2015, 10:26:10 AM, you wrote: > Hi Peter, > ptoye píše v Po 30. 11. 2015 v 04:28 -0700: >> There's an example below taken from >> https://wiki.documentfoundation.org/HelpContent#Make_Images_Appear which >> shows the problem: three of these paras use "allows to", three don't, but I >> think they all have the same meaning! > This is very easy to fix. wiki.documentfoundation.org is editable by > anyone who registers; so if you can register & log in, then you'll see a > small [edit] link next to the item that's wrong. > When you press it, it will lead you directly to the text - please just > correct it to use the correct English, check the draft, and publish it, > no approval by anybody is needed there. > Having said that; what is worse, we have these mistakes in the help > itself too. IIRC you told that it is hard for you to set up the git > repository - can we eg. meet on IRC to go through the process together, > so that you can make the improvements there too? > All the best, > Kendy -- To unsubscribe e-mail to: documentation+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/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-documentation] Re: Can I help?
Hi Lera, Thanks for your comments. As a first-time producer of LO documentation I wasn't sure about the MS Office reference. I put it in as many years ago I used Office, and found that the LO syntax rules for parameter names/prompts a bit confusing when I tried to put some spaces in. But I'm 100% happy for you to remove that paragraph. I realise that LO is nothing whatsoever to do with Office! "Designer/developer". No problem with changing it. Your wording is better. I should have thought of it. "User". We need some word to describe the person who is using the database, as opposed to the person developing it. After all, the concept of the parameter query was designed to allow the person using the database to input parameter values. Do you have a better word? Maybe recast the sentences using it to say something like "at run-time". If you prefer that I'll send a revised version in, but I think it will be difficult not to mention the fact that it's a human being that inputs the parameter value. Your English is better than my Russian! Best regards, Peter mailto:l...@ptoye.com www.ptoye.com - Monday, November 23, 2015, 6:31:21 PM, you wrote: > Hi Peter, > Your changes look very good. It really begins to look more professional and > easier to read and translate. Thank you a lot for your contribution. I can > prepare the patch in the nearest future. > I have only a few proposals. > We can not use a reference to an application of a competitive office suite > like > MS Access. In the official Help this looks very strange. If we assume that a > human can have difficulties in learning LibreOffice from habits to work with > another popular office application, we need to tell about differences, but > without using reference to this application. LibreOffice is not a fork of MSO. > There are many other office suites as GoogleDrive, GNOME Office, Calligra > Suite > etc. And we should not make a comparative table out of the Help. > I think that the sentence “For designers familiar with Access, the prompt is > more restricted as it cannot contain spaces or reserved characters.” needs > changing. > A mention of a user does not let the Help to look professional. In my opinion, > this can be done for a Guide or FAQ, but we need to avoid it, and to focus on > a functional description. > The last, for me “designers of a database” looks strange. I am used to see > “developers of a database”. I am not an English native speaker, and I can not > be sure, but when I get the order on a database, usually I am called > “developer”. I really don't know what we need to use in this case, just to > draw your attention. > What do you think about these? > Best regards, > Lera -- To unsubscribe e-mail to: documentation+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/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
