Re: [Gimp-developer] gimp-help-2 status
On Fri, 2003-12-19 at 13:21, Daniel Egger wrote: > Am Fre, den 19.12.2003 schrieb Sven Neumann um 19:55: > > > I am pretty sure it loads the DTD from disk if you provide it an XML > > catalog file that shows it where the DTD is found. This file is > > usually called /etc/xml/catalog. See http://xmlsoft.org/catalog.html > > I have this catalog file and xsltproc tries to open it, however it still > continues trying to load the files from net. This is a Debian unstable > system, all DTDs are installed and since some package created this file > I assumed that Debian would automagically make it work, but no > > Do you know where to modify the system to get it work? > > >"http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd";> > > catalog="/etc/xml/xml-core.xml"/> > systemIdStartString="http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"; > catalog="/etc/xml/xml-core.xml"/> > Is that (the above) everythin in your /etc/xml/catalog file? If so, then it's not really surprising that you are running out onto the Internet for everything -- the catalog file is essentially empty. Debian has unfortunately had very poor support for XML catalogs until quite recently. I don't know what the current level is like, since I do not use that distribution. As a start to repairing the problem, have a look at http://www.xmlsoft.org/buildDocBookCatalog which is a shell script to make the required entries for DocBook 4.1.2. If you have a different version of the DocBook DTDs installed (quite possible, since 4.2 is the latest release), you will need to tweak the script a little, but not much. Note that this script creates a separate catalog file and then adjusts /etc/xml/catalog to point to the newly created file (only) for DocBook lookups. That is the standard way to do this stuff, rather than populating /etc/xml/catalog with all your entries (makes packaging easier, too). It may be that the Debian DocBook DTD package already ships a catalog file, in which case you only need to add the appropriate lines to /etc/xml/catalog, which you can take out of the above script. If your catalog set up is working, then XInclude processing will also use it (libxml2 uses the catalogs by default). Cheers, Malcolm ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Friends of GNOME
Hi, David Neary <[EMAIL PROTECTED]> writes: > the change to GTK+ 2.2 and Fontconfig a few months ago. In > principle, someone who has the dependencies for a 2.0 build should > have everything they need to keep up with GIMP CVS through the 2.2 > release. We will have to depend on GTK+-2.4 pretty early if we want to make use of the new functionality it provides. Since there's a lot of very useful stuff in the 2.4 API, we should make the switch to GTK+-2.4 soon after the 2.0 release. > What do people think of the idea of a Friends of GIMP list that gets > added to the announce list when we make a release, for example? I thought that's what gimp-developer was for. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Quick progress report
Hi all, I don't have as much time as I'd hoped, so this is a quick report before bedtime. The 1.3 series is nearly at an end. If all goes well, we will have a 2.0 pre-release before Christmas, probably the end of the weekend or Monday. There are a number of issues still sitting on the 1.3 milestone, including some text tool improvements, the website migration, and a couple of small API changes. Nomis, who is working on the About dialog for 2.0, agrees that it's not a blocker for a pre-release, and in addition he won't have time to finish it until he celebrates the new year with his laptop :) The API changes are, in short, additions to the API which can be checked in very soon after the 2.0 release, or even before it if they're trivial enough. Since none of these will break existing scripts or plug-ins, I don't think that they could cause any problems. The text tool is, I think, good enough to be in a stable release. Sven had hoped to find the time to update it a little and add more of the features we would all like it to have, but as the ChangeLog shows, he has been very busy stabilising the tree, and fixing a large number of bugs which needed fixing before a stable release. These features will get scheduled for somewhere in the next few months, all going well. So there we have it. Barring a couple of small issues, we are ready for a pre-release. And given the current stability of the GIMP, I think that 2 or perhaps 3 pre-releases, with 2.0 before the end of January, is a realistic goal. That will lead us on to 2.2, and that's another thing we need to talk about. For the moment, the list of bugs on the 2.0 milestone has a number of bugs that should be fixed before we go 2.0. Many of these, though, can be fixed later on. The priority now, I think, is to get people using this piece of software we've built. Let out the GIMP! Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-help-2 status
Am Fre, den 19.12.2003 schrieb Sven Neumann um 19:55: > I am pretty sure it loads the DTD from disk if you provide it an XML > catalog file that shows it where the DTD is found. This file is > usually called /etc/xml/catalog. See http://xmlsoft.org/catalog.html I have this catalog file and xsltproc tries to open it, however it still continues trying to load the files from net. This is a Debian unstable system, all DTDs are installed and since some package created this file I assumed that Debian would automagically make it work, but no Do you know where to modify the system to get it work? http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd";> http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"; catalog="/etc/xml/xml-core.xml"/> -- Servus, Daniel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
[Gimp-developer] Friends of GNOME
Hi all, We are coming up to a release. I will post a detailed progress report, along with the current thinking that I have about the outstanding blockers. But this mail is about something else. Over the years since 1.2.0, or even since 1.2 pre1 (way back in April 1999) we have seen quite a few old "heads" drift away from the GIMP, either because they've become more active on other projects, or haven't got as much free time, or simply because they got into a big row and got pissed off. I think that 2.0 is an ideal opportunity to get some old GIMPers giving time to the project again. Some notable examples of people who have started to reappear recently, and should be welcomed with open arms, are Kelly and Jay. Some names that come easily to mind are syngin, adam, vidar, prof, bex, federico, and a bunch of others I'm forgetting. We're not going to dramatically break things again in the way that we did at the start of the 1.3 cycle, or even when we made the change to GTK+ 2.2 and Fontconfig a few months ago. In principle, someone who has the dependencies for a 2.0 build should have everything they need to keep up with GIMP CVS through the 2.2 release. So, I would like to put together a list of freinds of the GIMP, and get onto them and see if we can interest any of them in getting involved again. Can anyone think of names I've left off here? Several of these are certainly still on the devel list (if you are, shout). Many will probably request not to be sent any more mail. A few might help out a bit. So can I get names and e-mail addresses of people who were hanging around a while ago that you haven't seen since, and that you thought were cool? If so, could you send me a name and an e-mail address? What do people think of the idea of a Friends of GIMP list that gets added to the announce list when we make a release, for example? Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-help-2 status
Hi, Daniel Egger <[EMAIL PROTECTED]> writes: > Am Don, den 18.12.2003 schrieb Roman Joost um 15:53: > > > Hm.. i didn't had any memory problems with XInclude. If the encoding was > > wrong, the xsltproc throw an error and nothing more ... > > I still do, but only under Mac OSX. More annoying with XInclude is that > xsltproc cannot be taught to really load the DTD from disk and/or cache > the DTD so it doesn't need to repeat this step for every subdocument > again (including issuing another "error" message). I am pretty sure it loads the DTD from disk if you provide it an XML catalog file that shows it where the DTD is found. This file is usually called /etc/xml/catalog. See http://xmlsoft.org/catalog.html Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-help-2 status
Am Don, den 18.12.2003 schrieb Roman Joost um 15:53: > Hm.. i didn't had any memory problems with XInclude. If the encoding was > wrong, the xsltproc throw an error and nothing more ... I still do, but only under Mac OSX. More annoying with XInclude is that xsltproc cannot be taught to really load the DTD from disk and/or cache the DTD so it doesn't need to repeat this step for every subdocument again (including issuing another "error" message). -- Servus, Daniel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: [Gimp-developer] gimp-help-2 - TODOs and ideas
Am Don, den 18.12.2003 schrieb Roman Joost um 16:10: > > Huh? Probably it's just me being dense... > Heh - no. I shouldn't write mails during a lecture ... The existing XML > files are renamed to the name of the help ids in > $GIMP/app/widgets/gimphelp-ids.h, eg: airbrush.xml is now: > tool-airbrush.xml Aha, cool. > I'll have a look at it ... Can you please add it to the Wiki as recommended lecture for anyone who want to help with the technical side of the documentation. I'm already in a rush again -- Servus, Daniel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
