I (and I suspect most other readers) DO actually appreciate you taking the time to discuss these formats online. Still, I can understand (and agree with) the reasons which are driving people to be somewhat abrasive in some of the posts. Microsoft has definitively proven that it will do whatever it can to lock its customers in and avoid competing on technical (and now price) merits.

This is actually not true, although I have seen people make this mistake before. It actually is fully valid XML, it's just not the same architectural approach you've seen from the traditional DocBook model of document formats. Since folks do ask this question though, and here are a few themes I think folks are getting at when asking this question:

Don't be lazy, take construct a FileReader first, after build, close it. This will solve too many files open problem. This is extremely important to busy websites. The resources will be used really quickly. You don't DOS (deny of services) by your own mistake. Your original code will never close the valuable resources. Big no-no. The traverseDoc() method gives you a simplified traversal. Java Source file package com.example; import org.jdom.Document; import org.jdom.Element; import org.jdom.

This means you that you are using an outdated version of Acrobat Reader. FoodSmart records are in Acrobat version 5, so you need Acrobat Reader version 5. To get a free up-to-date version return to FoodSmart, click on the yellow icon "Get Acrobat Reader", and follow the instructions. Once installed on your computer you will be able to view and print the record.

This is a work in progress. If you are reading a local copy, the master copy might be newer. This document uses are relative links; if they don't work, please use the master copy. Please feel free to ask questions and/or provide answers; send email to the Docutils-users mailing list. Project members should feel free to edit the source text file directly.

To open PDF files (often indicated by the Adobe Acrobat icon), you must have the Adobe Acrobat Reader software installed on your computer. This software is available from Adobe Systems Incorporated. Some PDF files require the latest version of the Adobe Acrobat Reader. You can download the reader free from the Adobe Systems Inc. web site. For more information, visit http://www.adobe.com.

Here's some sample code for that: PropertyValue [] mypv = new PropertyValue[1]; mypv[0] = new PropertyValue(); mypv[0].Name = new String("FilterName"); mypv[0].Value = new String("scalc: Text - txt"); mypv[0].Handle = -1; mypv[0].State = PropertyState.DEFAULT_VALUE; aStore.storeAsURL(doc, mypv); //aStore is a XStorable object, and doc is url string

The CD-ROM's main document, FS_2002.PDF, is an Adobe AcrobatTM document. You need to have the Acrobat ReaderTM installed on your computer in order to read the document. The reader software is free and available at www.adobe.com. We also included the latest version (as of December 2002) for Windows 95, 98, NT and 2000 on the CD-ROM.

Yes. The Document Assistant is a mobile and desktop XML editor but it hides all of XMLs complexity from the end user. The Document Assistant can edit any well formed XML document based on an imported DTD. The software is more sophisticated compared to the limited DTD standard and so it provides additional XML features for the developer and end user.

Data and document XML are two different ways of representing the same XML information. The Document Assistant software produces both Data and Document XML. Data XML stores all the information in a structured way which is machine readable so it can query, analyze or produce graphical information easily. In contrast, Document XML is used to represent information in a format that can be published and printed. English language is produced within the Document XML.

Here's some sample code for that: sub SaveXML dim mProps(0) as new com.sun.star.beans.PropertyValue mProps(0).Name = "FilterName" 'This works with 614 mProps(0).Value = "swriter: StarOffice XML (Writer)" oDesk = createUNOService("com.sun.star.frame.Desktop") 'For some reason, ActiveComponent no longer works: oComponent = oDesk.CurrentComponent() oComponent.storeAsUrl("file:///C|/Tmp/startemp.xml",_ mProps()) end sub

I played hooky and ploughed through the Metro specification. Interesting. I satisfied myself that there are ways to anticipate this format in some "package" applications I have in mind, and they should be able to be Metro hybrids in the future. I know what names not to use to avoid future collisions, in particular [;<).

The WithXmlDoc example in bakery/examples/ shows how to subclass from Document_XML so that your Document can use an XML format. This document explains how to use Document_XML. Don't worry, you don't need to do much of it. And it is very useful in this case. Bakery classes do not need to inherit from classes that share a common base class (Bakery::View is not a Gtk widget) so the situation is not complicated.

Yes, by adding a 'format=xml' in the URL like so: http://search.cpan.org/search?mode=module&format=xml&query=LWP This feature is NOT supported and it may change at any time so don't build applications to depend on its continued presence.

If the file type appears in the Save dialog but is grayed out, you may need to change the image type. For instance, you can't save an RGB as a GIF (convert to indexed first) or an indexed image to JPEG (convert to RGB first). GIMP comes with full support for a few types built in. If the type you want doesn't appear in file type format of the Open and Save dialogs, you need to check the Plug-in registry to see whether you need to download an optional plug-in.

XML is a meta-language optimized for use on the Internet. A meta-language provides a way to create other languages or vocabularies. Many applications use XML as a way of sharing data between otherwise incompatible systems.

Some imaging systems will allow you to display multiple documents, with the number of documents you can have opensimultaneously limited only by the amount of memory available.