RSS/Atom feed Twitter
Site is read-only, email is disabled

Acknowledgments

This discussion is connected to the gimp-docs-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

6 of 6 messages available
Toggle history

Please log in to manage your subscriptions.

Acknowledgments Roman Joost 16 Nov 09:59
  Acknowledgments Alexandre Prokoudine 16 Nov 19:19
Acknowledgments Marco Ciampa 17 Nov 12:53
  Acknowledgments Roman Joost 22 Nov 09:07
   Acknowledgments Sven Neumann 22 Nov 16:57
    Acknowledgments Roman Joost 25 Nov 10:08
Roman Joost
2009-11-16 09:59:12 UTC (about 15 years ago)

Acknowledgments

Hi folks,

just want to pass on a big thank you for the manual. I'm currently in New Zealand attending the Kiwi Pycon, a python conference. I got fantastic feedback for the manual, which I want to pass on to all who contributed.

Cheers!

Alexandre Prokoudine
2009-11-16 19:19:34 UTC (about 15 years ago)

Acknowledgments

Thank you. We've been missing you, mate :)

Alexandre

On 11/16/09, Roman Joost wrote:

Hi folks,

just want to pass on a big thank you for the manual. I'm currently in New Zealand attending the Kiwi Pycon, a python conference. I got fantastic feedback for the manual, which I want to pass on to all who contributed.

Cheers!
--
Roman Joost
www: http://www.romanofski.de
email: romanofski@gimp.org

Marco Ciampa
2009-11-17 12:53:27 UTC (about 15 years ago)

Acknowledgments

On Mon, Nov 16, 2009 at 06:59:12PM +1000, Roman Joost wrote:

Hi folks,

just want to pass on a big thank you for the manual. I'm currently in New Zealand attending the Kiwi Pycon, a python conference. I got fantastic feedback for the manual, which I want to pass on to all who contributed.

Cheers!

Much of the merit is for you (IMHO)....

About acknowledgements ... I would like to post a desiderata. The national versions of the manual are currently missing an aknowledgement paragraph about the current language team. I mean that when someone find something wrong or missing in the language version of the manual he/her have to browse through many authors/proof readers in search of the proper people to contact, with many trial & errors with authors that are not currently active on the manual or looking for a missing tranlators mailing list. I think this is confusing.

I suggest to create a new tag like this:

* Content Writers * Proof Reading
* Graphics, Stylesheets
* Build System, Technical Contributions

added

* Current language team & support (or any appropriate section title) Team leader (if any), translator email, translator email, language team mailing list (if any).

What do you think about it?

--

Marco Ciampa

+--------------------+ | Linux User #78271 |
| FSFE fellow #364 |
+--------------------+

Roman Joost
2009-11-22 09:07:50 UTC (about 15 years ago)

Acknowledgments

Hi Marco,

On Tue, Nov 17, 2009 at 12:53:27PM +0100, Marco Ciampa wrote:

On Mon, Nov 16, 2009 at 06:59:12PM +1000, Roman Joost wrote:

Hi folks,

just want to pass on a big thank you for the manual. I'm currently in New Zealand attending the Kiwi Pycon, a python conference. I got fantastic feedback for the manual, which I want to pass on to all who contributed.

Cheers!

Much of the merit is for you (IMHO)....

About acknowledgements ... I would like to post a desiderata. The national versions of the manual are currently missing an aknowledgement paragraph about the current language team. I mean that when someone find something wrong or missing in the language version of the manual he/her have to browse through many authors/proof readers in search of the proper people to contact, with many trial & errors with authors that are not currently active on the manual or looking for a missing tranlators mailing list. I think this is confusing.

I suggest to create a new tag like this:

* Content Writers * Proof Reading
* Graphics, Stylesheets
* Build System, Technical Contributions * Current language team & support (or any appropriate section title) Team leader (if any), translator email, translator email, language team mailing list (if any).

Just wondering: do you refer to the authors.xml or the manual itself?

If it's the authors.xml - I remember we used the stylesheet from GIMP and I guess - without having made any research - that the stylesheet which is processing the authors.xml doesn't rely on any standard. If that's the case, I guess we can put any information we want to provide in this file.

Another idea I had: what about the homepage (docs.gimp.org) itself?

Cheers,

Sven Neumann
2009-11-22 16:57:50 UTC (about 15 years ago)

Acknowledgments

Hi,

On Sun, 2009-11-22 at 18:07 +1000, Roman Joost wrote:

If it's the authors.xml - I remember we used the stylesheet from GIMP and I guess - without having made any research - that the stylesheet which is processing the authors.xml doesn't rely on any standard.

The authors.xml file in GIMP uses Dublin Core (see http://dublincore.org/). Of course you can diverge from this, if there's a need. But it might be a good idea to check if the Dublin Core Metadata standard provides what you are looking for.

Sven

Roman Joost
2009-11-25 10:08:35 UTC (about 15 years ago)

Acknowledgments

On Sun, Nov 22, 2009 at 04:57:51PM +0100, Sven Neumann wrote:

Hi,

On Sun, 2009-11-22 at 18:07 +1000, Roman Joost wrote:

If it's the authors.xml - I remember we used the stylesheet from GIMP and I guess - without having made any research - that the stylesheet which is processing the authors.xml doesn't rely on any standard.

The authors.xml file in GIMP uses Dublin Core (see http://dublincore.org/). Of course you can diverge from this, if there's a need. But it might be a good idea to check if the Dublin Core Metadata standard provides what you are looking for.

Thanks for pointing that out. We should certainly have a look into that.

Cheers,