|
From: laszlo k. <las...@su...> - 2000-10-19 18:18:34
|
> This is excellent news! :) I need to check out the code sometime soon. I was > just curious, but perhaps this should be announced to various Documentation > projects (just in case people want to throw in their comments and/or want to > contribute). Of course this should only be done when the code is in a "state" > to accept contributions. The biggest problem is probably that is not that easy to test it as there is not much documentation out there with the related OMF files. Maybe we should generate some and put them on the project web page? There is a quite large number of OMF files in the OMF repository (link from the project web site). Otherwise the code is ready to be tried. > Umm - the OMF file is an XML file, correct? libxml should handle validation I > believe (assuming you are using the DOM parser) ? > > Even if you are using the SAX parser you can enable validation but it is kind > of "ugly". I am using the SAX parser and I was thinking about a DTD based validation. I don't know if libxml supports anything like this. [snip] > > The Scrollkeeper files go into prefix/var/lib/scrollkeeper. > > Umm - which scrollkeeper files are you talking about? Are these the OMF files? > Shouldn't they go into prefix/share/scrollkeeper? No, these are the files generated by Scrollkeeper and passed away to the Help Browser. The OMF files are not moved by the current implementation. > How are the OMF tags different than the OS locales? OMF language tags are described here: http://www.landfield.com/rfcs/rfc1766.html They are much broader and have a bit different format than the locales (like en-US in OMF and en_US as OS locale). Laszlo |