Re: [Gimp-developer] wtf with the download?
Are people going to read the fine print or just pick their favourite colour? Perhaps the second option might read GIMP Torrent. On Sun, May 31, 2015 at 7:43 AM, C R wrote: > I have developed the html for the buttons. A test can be found here: > http://opendesignstudio.org/gimp/samples/ > > Note I have also changed the text a bit to reflect Michael's latest > comments: http://opendesignstudio.org/gimp/samples/ > > Note also that the links to not ink to real files, as I have set them to > the git repository values, which are replaced with the urls on the backend. > > Comments? > > On Wed, May 27, 2015 at 9:32 PM, Michael Schumacher wrote: > >> >> >> On 05/14/2015 08:47 AM, C R wrote: >> >> Hi, >> >> > To save retyping, here is the current text: >> >> we do not really have to worry about bandwidth usage (could be that the >> webserver config is the limiting factor) and especially not about fees. >> >> This allows us to make the texts a bit easier, and focus on the user >> experience: >> >> > This link downloads the GIMP executable for Windows platforms via >> gimp.org. It >> > can be a bit slow at times, so if you are having problems, try the >> > link below for download via BitTorrent >> >> For BitTorrent, all of our torrents are set up with multiple web seeds, >> so this will work even without seeders. As I wrote before , we tested >> this in a university network at a conference, where torrent traffic was >> blocked, and it did work this way). >> >> > BitTorrent is a peer-to-peer file sharing system. >> > BitTorrent works by downloading GIMP from a distributed network of >> > mirror sites and from other BitTorrent users called "seeders". Learn >> more... >> >> What would be nice to have is a diff to the current download site (or >> maybe even only the Windows.htrw part of it). >> >> >> -- >> Regards, >> Michael >> GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD >> ___ >> gimp-developer-list mailing list >> List address:gimp-developer-list@gnome.org >> List membership: >> https://mail.gnome.org/mailman/listinfo/gimp-developer-list >> List archives: https://mail.gnome.org/archives/gimp-developer-list >> > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp in private schools and educational institutions
On Wed, Apr 29, 2015 at 1:47 PM, Nathan Summers wrote: > I wouldn't have wanted my name associated with something called "GIMP" > if I had known what the word meant when I started contributing to it. gimp noun 1. twisted silk, worsted, or cotton with cord or wire running through it, used chiefly as upholstery trimming. (in lacemaking) coarser thread that forms the outline of the design in some techniques. 2. fishing line made of silk bound with wire. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp in private schools and educational institutions
How do we know that the word "Gnu" is not offensive in some schools in some culture in some language? Also, the word "manipulation" has negative connotations for some people in some cultures .. On Sat, Apr 18, 2015 at 10:55 PM, Liam R. E. Quin wrote: > On Wed, 2015-04-08 at 12:58 -0500, Sam Bagot wrote: >> A product called Gimp can't be used [in schools] > > > Although GIMP can be used in at least some schools, I agree with your > premise. > > These conversations always seem to run the same course: > > A: the name GIMP is offensive to me, or to people with whom I work. B: > No. The name GIMP is not offensive. > A: yes it is. > B: It doesnt offend me, and your opinion doesn't matter to me. A: We > like the name. Bye. > > For my own part I have some hesitation - for example, I am not about > to go to a meeting on making the Web accessible to people with special > needs while wearing a "GIMP" tee-shirt, and obviously can't promote > GIMP usage too openly at work. If it was called "Wilber", or maybe > "Nazi" or "Spic" or "Hun"... hmm, no, not those last three perhaps, > but Wilber would be OK. > > The "brand" argument doesn't really cut much ice - plenty of other > Free and proprietary applications have been renamed in the past, and > the publicity can increase visibility. > > Maybe instead of GIMP 3.0 we could have a Goat Rainbow 1.0 or > something? > > But then you get into endless discussions about the name. > > In the meantime, for school use, could you refer to the program as the > GNU Image Manipulation Program, and if people comment on GIMP explain > it's short for the longer name as that's too long to use everywhere? > > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] MWG composite functions & gexiv2
The good news is that exiv2 already handles some of these conversions! See here for the details: http://dev.exiv2.org/issues/1050 The bad news is that I still haven't developed the coding skills to do all the necessary conversions. Help ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] MWG composite functions & gexiv2
> Apologies. Let's try without attachments! As a picture is worth a thousand words, I built a mockup based on the GIMP metadata editor. The Exif tab has been left alone as a lot of that data comes straight from the camera. The XMP and IPTC tabs have been merged and separated into tabs called: Who, What, Where, When according to Metadata Working Group guidelines. Under the hood, gexiv2 composite functions would be used to read and write to the correct metadata fields. Results can be seen on the following links: http://www.vcn.bc.ca/~apater/01who.png http://www.vcn.bc.ca/~apater/02what.png http://www.vcn.bc.ca/~apater/03where.png http://www.vcn.bc.ca/~apater/04when.png ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] MWG composite functions & gexiv2
Apologies. Let's try without attachments! As a picture is worth a thousand words, I built a mockup based on the GIMP metadata editor. The Exif tab has been left alone as a lot of that data comes straight from the camera. The XMP and IPTC tabs have been merged and separated into tabs called: Who, What, Where, When according to Metadata Working Group guidelines. Under the hood, gexiv2 composite functions would be used to read and write to the correct metadata fields. Results can be seen on the following links: http://www.vcn.bc.ca/~apater/01who.png http://www.vcn.bc.ca/~apater/02what.png http://www.vcn.bc.ca/~apater/03where.png http://www.vcn.bc.ca/~apater/04when.png ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] MWG composite functions & gexiv2
As a picture is worth a thousand words, I built a mockup based on the GIMP metadata editor. The Exif tab has been left alone as a lot of that data comes straight from the camera. The XMP and IPTC tabs have been merged and separated into tabs called: Who, What, Where, When according to Metadata Working Group guidelines. Under the hood, gexiv2 composite functions would be used to read and write to the correct metadata fields. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] MWG composite functions & gexiv2
On Fri, Mar 20, 2015 at 12:41 AM, Alan Pater wrote: > I have been talking with Jim Nelson about adding composite functions > to gexiv2. These would be based on Metadata Working Group guidelines > with the addition of a couple of commonly-requested formats. > >https://bugzilla.gnome.org/show_bug.cgi?id=712429 > > Here is a link to the MWG Guidelines: > http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf > In the hope of finding a real developer to help with this, I have put together a quick list of bugs from various projects that, I think, would benefit from this work. Specifically what I need help with are writing a few conversion functions, for example from xml to a separated string. Any volunteers? // GIMP bugs https://bugzilla.gnome.org/page.cgi?id=browse.html&product=gimp Bug 118202 - [TRACKING BUG] Metadata improvements Bug 61499 - easy way to view/edit image metadata (author, copyright, image title, etc.) Bug 727270 - Proposal to add gimp_metadata_set_from_iptc Bug 349224 - Creative Commons licenses integration // Shotwell bugs https://bugzilla.gnome.org/page.cgi?id=browse.html&product=shotwell Bug 718518 - Move EXIF date handling logic into gexiv2 Bug 717172 - view/edit all photo metadata Bug 719173 - Read face 'tags' from Samsung Galaxy S3 mobile photos Bug 717713 - Shotwell fails to split a comma separated keyword list during import from XMP-dc:Subject Bug 718107 - Xmp.dc.description or Iptc.Application2.Caption is not imported with accented characters Bug 731255 - Inconsistency in reporting date after editing it. Bug 735069 - Shotwell overwrites time stamps in metadata when those are changed outside shotwell // gexiv2 bugs https://bugzilla.gnome.org/page.cgi?id=browse.html&product=gexiv2 Bug 712463 - Some date formats in the wild do not conform to EXIF standard. Bug 737495 - Add support for Exif.GPSInfo.GPSTimeStamp / Rational [3] Bug 723794 - "Unsupported time format" error when loading image w/ Darwin Core metadata Bug 712431 - Add milliseconds to get_date_time() in GExiv2.py Bug 712430 - GDateTime accessor // eog bugs https://bugzilla.gnome.org/page.cgi?id=browse.html&product=eog Bug 515265 - use exiv2 as metadata source Bug 719621 - Rotating image destroys XMP and IPTC metadata Bug 341653 - Add support for IPTC-NAA Bug 699297 - Image Properties should prominently show Title and Comments // Nautilus bugs https://bugzilla.gnome.org/page.cgi?id=browse.html&product=nautilus Bug 729685 - edit, metadata, music, photos. // sushi bugs https://bugzilla.gnome.org/page.cgi?id=browse.html&product=sushi Bug 730391 - EXIF orientation information incorrectly interpreted for CR2 (Canon RAW) files // gthumb bugs https://bugzilla.gnome.org/page.cgi?id=browse.html&product=gthumb 28 bugs found Bug 669026 - Changing metadata does not change file modification time Bug 456699 - Geotagging on GThumb Bug 417824 - Sorting images by Comment Date Bug 621478 - Changing EXIF date corrupts the JPEG thumbnail ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] MWG composite functions & gexiv2
A few more details on this project. By including MWG guidelines at the shared library level, current and future applications can all benefit and don't have to reinvent the wheel. I guess what I am looking for is a mentor to guide me through the code and provide a coding basis for some of the conversion functions. https://bugzilla.gnome.org/show_bug.cgi?id=712429 On Fri, Mar 20, 2015 at 4:07 PM, Alan Pater wrote: > I have gone ahead with the first patch of the series, adding the > xmp.dc.description property to the get_comment function in gexiv2. > Comments and testers are very welcome. > > https://bugzilla.gnome.org/show_bug.cgi?id=746424 > > On Fri, Mar 20, 2015 at 12:41 AM, Alan Pater wrote: >> I have been talking with Jim Nelson about adding composite functions >> to gexiv2. These would be based on Metadata Working Group guidelines >> with the addition of a couple of commonly-requested formats. >> >>https://bugzilla.gnome.org/show_bug.cgi?id=712429 >> ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] MWG composite functions & gexiv2
I have gone ahead with the first patch of the series, adding the xmp.dc.description property to the get_comment function in gexiv2. Comments and testers are very welcome. https://bugzilla.gnome.org/show_bug.cgi?id=746424 On Fri, Mar 20, 2015 at 12:41 AM, Alan Pater wrote: > I have been talking with Jim Nelson about adding composite functions > to gexiv2. These would be based on Metadata Working Group guidelines > with the addition of a couple of commonly-requested formats. > >https://bugzilla.gnome.org/show_bug.cgi?id=712429 > > I can do a lot of the grunt work and testing, but need a hand with > some of the conversions, from xml for example. Who would like to > volunteer to give me a hand? > > I think it makes sense to do this work in gexiv2, that way all the > individual applications don't have to maintain duplicate code for > these functions themselves. And by abiding to MWG standards, everyone > doesn't have to reinvent the wheel and come up their own set of common > metadata properties. > > Here is a link to the MWG Guidelines: > http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf > > My thoughts are to also include support for reading proprietary > metadata from ACDSee, as there appears to be a lot of requests from > users of that Windows app to migrate to a Free Software alternative. > > Volunteers? > > Cheers, > Alan > > On Thu, Mar 19, 2015 at 10:19 PM, Jim Nelson wrote: >> Alan, >> >> I would like to ask if I should jump and provide patches for MWG composite >> tag functions in gexiv2? >> >> >> That would be great. I agree with your comment there, this seems to be a >> no-brainer. >> >> My coding skills are quite basic, but this work looks like a reasonable >> match for me. I would need a bit of help with some of the more complex data >> conversions. Is this something likely to be incorporated on a timely basis? >> Are there resources available to test my work? >> >> >> Unfortunately, the time I can offer toward gexiv2 is extremely limited. If >> you need help, I would recommend reaching out to other contributors (either >> directly or on the gexiv2 mailing list) for guidance. In particular, the >> GIMP project may be interested in your work, now that GIMP has a hard >> dependency on gexiv2. Michael Natterer and Jehan Pages are the first people >> I would contact. >> >> I have gone ahead and added a couple of fields to the existing set_comment >> function in gexiv2. >> >> >> I'll take a look at your patch. >> >> -- Jim ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] MWG composite functions & gexiv2
I have been talking with Jim Nelson about adding composite functions to gexiv2. These would be based on Metadata Working Group guidelines with the addition of a couple of commonly-requested formats. https://bugzilla.gnome.org/show_bug.cgi?id=712429 I can do a lot of the grunt work and testing, but need a hand with some of the conversions, from xml for example. Who would like to volunteer to give me a hand? I think it makes sense to do this work in gexiv2, that way all the individual applications don't have to maintain duplicate code for these functions themselves. And by abiding to MWG standards, everyone doesn't have to reinvent the wheel and come up their own set of common metadata properties. Here is a link to the MWG Guidelines: http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf My thoughts are to also include support for reading proprietary metadata from ACDSee, as there appears to be a lot of requests from users of that Windows app to migrate to a Free Software alternative. Volunteers? Cheers, Alan On Thu, Mar 19, 2015 at 10:19 PM, Jim Nelson wrote: > Alan, > > I would like to ask if I should jump and provide patches for MWG composite > tag functions in gexiv2? > > > That would be great. I agree with your comment there, this seems to be a > no-brainer. > > My coding skills are quite basic, but this work looks like a reasonable > match for me. I would need a bit of help with some of the more complex data > conversions. Is this something likely to be incorporated on a timely basis? > Are there resources available to test my work? > > > Unfortunately, the time I can offer toward gexiv2 is extremely limited. If > you need help, I would recommend reaching out to other contributors (either > directly or on the gexiv2 mailing list) for guidance. In particular, the > GIMP project may be interested in your work, now that GIMP has a hard > dependency on gexiv2. Michael Natterer and Jehan Pages are the first people > I would contact. > > I have gone ahead and added a couple of fields to the existing set_comment > function in gexiv2. > > > I'll take a look at your patch. > > -- Jim ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
