On Monday, January 07, 2013 05:17:41 Park Shinjo wrote: > Unfortunately the documentation is in Korean[1] (about 460 pages), we need > translation of the document in English. Some of developers also criticized > details of specification document, since some part of spec does not match > with actual implementation and some parts are missing in the document. > > The downloaded file is zipped, and its file name is encoded into EUC-KR. > You need to unzip this file with proper encoding support. > > [1] > http://www.hancom.co.kr/downLoad.downView.do?targetRow=1&seqno=3202&mcd_sav > e=005
Now that's a challenge for google translate if I ever saw one. :) Thanks for the link. And regarding the faulty spec, that's more or less common behaviour. It happens everywhere and most of the time it's just a mistake due to rushed deadlines or misunderstandings on the side of the documenter. I suppose there will be future revisions to fix them. -Inge > 2013/1/7 Inge Wallin <i...@lysator.liu.se> > > > On Monday, January 07, 2013 01:30:52 Park Shinjo wrote: > > > So, as far as I understand, I can take the pole.(cpp|h) code (possibly > > > synchronize often with libmso) and need to build my own library for > > > handling HWP document. Thumbnailing and metadata extraction only needs > > > to read some part of entire document, I can tune for that kind of > > > processing in external program too. > > > > Yes, that would be one way to work. Naturally we would be very grateful > > if you committed any improvements to pole that you create in your work. > > > > > Hope I can revive HWP backend for Calligra :) > > > > That would be even greater. :) > > > > Do you have a pointer to the documentation? Is it in English or do you > > have to > > know Korean to be able to understand it? > > > > -Inge > > > > > > Regards, > > > Park Shinjo > > > > > > > > > 2013/1/7 <matus.u...@gmail.com> > > > > > > > Hi, > > > > > > > > compared to the latest version found at [1], the version of POLE > > > > inside libmso includes a number of bug fixes and code to detect > > > > invalid and corrupt files in the Windows Compound Binary File > > > > Format. It's not maintained as a separate library, It's simply part > > > > of libmso. And you should know it's fine tuned to files produced by > > > > MS Office, so it might be required to disable a bunch of blocks of > > > > code. > > > > > > > > In Calligra, libgsf has been superseded by libmso. > > > > > > > > Check the powerpoint or msword-odf filter for proper usage. Look for > > > > the > > > > > > readStream function in the mswordodfimport.cpp file, which reads a > > > > stream > > > > > > from a specific storage into a buffer. > > > > > > > > [1] http://pole.berlios.de/ > > > > > > > > br, > > > > > > > > -matus > > > > > > > > On Sun, Jan 6, 2013 at 5:32 PM, Park Shinjo <k...@peremen.name> wrote: > > > >> Hello, This is my first message to this list. > > > >> > > > >> I am working on Hancom Word (mostly known as HWP) support on KDE > > > >> environment. Haansoft has released specifications of its HWP file > > > > format > > > > > >> in late 2010, making HWP support outside of Hancom Word possible. > > > >> > > > >> The HWP document is based on Microsoft OLE compound document format, > > > > and > > > > > >> currently Calligra Words uses POLE (as far as I know) for parsing > > > >> this format. Since its internal structure is different from any > > > >> other kind > > > > of > > > > > >> files, and I want to reuse code as much as possible, I want to ask > > > > some > > > > > >> questions for POLE. > > > >> > > > >> 1) How can I use POLE library outside of Calligra? I am currently > > > >> working on thumbnailer and metadata indexer of HWP format, and it > > > >> currently uses libgsf. For further integration with Calligra, I want > > > > to > > > > > >> switch codebase to what Calligra currently uses. Rendering of > > > >> document is not necessarily required here, since HWP file contains > > > >> preview > > > > image > > > > > >> and text. I'm also interested in implementing viewer function inside > > > >> Okular too. > > > >> > > > >> 2) Is POLE library inside libmso considered as "upstream"? I have > > > > found > > > > > >> implementation of POLE outside of Calligra, but it seems that code > > > >> is not exactly same as Calligra's code. > > > >> > > > >> I am not "yet" interested for restoring hancomword importer (and > > > >> maintain it) in Calligra words, as there's no real code now. > > > >> Choosing right codebase will help integration, so I'm asking how I > > > >> can handle OLE compound document via POLE. > > > >> > > > >> Regards, > > > >> Park Shinjo > > > >> > > > >> _______________________________________________ > > > >> calligra-devel mailing list > > > >> calligra-devel@kde.org > > > >> https://mail.kde.org/mailman/listinfo/calligra-devel > > > > > > > > _______________________________________________ > > > > calligra-devel mailing list > > > > calligra-devel@kde.org > > > > https://mail.kde.org/mailman/listinfo/calligra-devel > > > > _______________________________________________ > > calligra-devel mailing list > > calligra-devel@kde.org > > https://mail.kde.org/mailman/listinfo/calligra-devel _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel