Re: [hugin-ptx] Purpose of this list

2024-04-18 Thread Chris
[image: davi...@gmail.com's profile photo]
davi...@gmail.com
Thank you for your careful reading of my posts, your understanding of the 
reason behind my questions and your support.
Chris


On Thursday, April 18, 2024 at 11:15:02 AM UTC+1 davi...@gmail.com wrote:

> Le 18/04/2024 à 09:19, Greg 'groggy' Lehey a écrit :
>
> On Wednesday, 17 April 2024 at 23:39:07 -0700, Chris wrote:
>
> T.Modes, Wie du sicher weißt, bedeutet das deutsche Wort "Gift" etwas ganz
> anderes als das englische Wort "gift" :).
> Vielleicht sind die Worte "impliziert" und "implies" falsche Freunde - sie
> haben etwas unterschiedliche Bedeutungen.
>
> (As I am sure you are aware, the German word "Gift" means something quite
> different to the English word "gift" :).
> Perhaps the words "impliziert" and "implies" are false friends - they have
> rather different meanings.)
> On Wednesday, April 17, 2024 at 7:33:51 AM UTC+1 Chris wrote:
>
>
> Chris, I've seen a lot of messages from you.  This one seems to be the
> second one with identical content.  And most of them seem to have
> nothing to do with the software.
>
> If you feel that you have to attack T.Modes, please do it privately.
>
>
> Greg,
>
> Chris has repeatedly stated that his questions and remarks were about the 
> documentation. While I agree they don't have anything to do with the 
> coding, they do have to do with the software because documentation IMO 
> should be considered as being part of the software. If a documentation 
> tells me something (I am not speaking of the Hugin documentation here) and 
> the software does something else, then this is a bug. I agree this would be 
> a documentation bug, not a coding bug, but it would still be a bug. Or 
> maybe the word "bug" is not appropriate here. Anyhow documentation issues 
> should be addressed just like coding bugs should be fixed.
>
> About your second paragraph: I don't feel that Chris has attacked Thomas. 
> I saw Chris insisting on documentation issues. It happens that Thomas was 
> almost the only one to answer, but I did not feel anything personal in 
> Chris' mails. 
>
> I am glad that someone is checking the exact formulation of the 
> documentation. I don't know who wrote the documentation (although I would 
> not be surprised if it was Thomas), but I know that developers are seldom 
> good documentation writers. I am a software developer, I have tried to 
> write documentation and I don't think I ever achieved something which was 
> simultaneously short enough, clear enough and unambiguous. It is very 
> difficult for a developer to realize that people could understand what he 
> wrote differently from what he meant. It is even more difficult for him to 
> find all the sentences where such gap could exist. 
>
> I know that all the documentation was written by volunteers doing it on 
> their free time (just like the code). Improving the documentation takes 
> time, and the resources are limited. I guess that Thomas enjoys much more 
> coding than writing documentation (I do!).
>
> I enjoyed this discussion up to now because it has taught me a few things 
> about English. And I would appreciate improving the documentation in this 
> way because I am always wary about what I am understanding from a 
> documentation written by someone whose native language is probably not 
> English, even more so because it is not mine either.
>
>
>
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/aa65b98a-9993-4539-86a2-4c316ee90439n%40googlegroups.com.


Re: [hugin-ptx] Purpose of this list

2024-04-18 Thread Frédéric Da Vitoria

Le 18/04/2024 à 09:19, Greg 'groggy' Lehey a écrit :

On Wednesday, 17 April 2024 at 23:39:07 -0700, Chris wrote:

T.Modes, Wie du sicher weißt, bedeutet das deutsche Wort "Gift" etwas ganz
anderes als das englische Wort "gift" :).
Vielleicht sind die Worte "impliziert" und "implies" falsche Freunde - sie
haben etwas unterschiedliche Bedeutungen.

(As I am sure you are aware, the German word "Gift" means something quite
different to the English word "gift" :).
Perhaps the words "impliziert" and "implies" are false friends - they have
rather different meanings.)
On Wednesday, April 17, 2024 at 7:33:51 AM UTC+1 Chris wrote:

Chris, I've seen a lot of messages from you.  This one seems to be the
second one with identical content.  And most of them seem to have
nothing to do with the software.

If you feel that you have to attack T.Modes, please do it privately.


Greg,

Chris has repeatedly stated that his questions and remarks were about 
the documentation. While I agree they don't have anything to do with the 
coding, they do have to do with the software because documentation IMO 
should be considered as being part of the software. If a documentation 
tells me something (I am not speaking of the Hugin documentation here) 
and the software does something else, then this is a bug. I agree this 
would be a documentation bug, not a coding bug, but it would still be a 
bug. Or maybe the word "bug" is not appropriate here. Anyhow 
documentation issues should be addressed just like coding bugs should be 
fixed.


About your second paragraph: I don't feel that Chris has attacked 
Thomas. I saw Chris insisting on documentation issues. It happens that 
Thomas was almost the only one to answer, but I did not feel anything 
personal in Chris' mails.


I am glad that someone is checking the exact formulation of the 
documentation. I don't know who wrote the documentation (although I 
would not be surprised if it was Thomas), but I know that developers are 
seldom good documentation writers. I am a software developer, I have 
tried to write documentation and I don't think I ever achieved something 
which was simultaneously short enough, clear enough and unambiguous. It 
is very difficult for a developer to realize that people could 
understand what he wrote differently from what he meant. It is even more 
difficult for him to find all the sentences where such gap could exist.


I know that all the documentation was written by volunteers doing it on 
their free time (just like the code). Improving the documentation takes 
time, and the resources are limited. I guess that Thomas enjoys much 
more coding than writing documentation (I do!).


I enjoyed this discussion up to now because it has taught me a few 
things about English. And I would appreciate improving the documentation 
in this way because I am always wary about what I am understanding from 
a documentation written by someone whose native language is probably not 
English, even more so because it is not mine either.



--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/312e2b1c-fa56-492f-8617-a77e6664780d%40gmail.com.