<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Complete compatibility with Hancom Office file formats" href="https://bugs.documentfoundation.org/show_bug.cgi?id=128907#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Complete compatibility with Hancom Office file formats" href="https://bugs.documentfoundation.org/show_bug.cgi?id=128907">bug 128907</a> from <a class="email" href="mailto:qkrrbals1375@gmail.com" title="PGM <qkrrbals1375@gmail.com>"> PGM</a> <pre>(In reply to Mike Kaganski from <a href="show_bug.cgi?id=128907#c10">comment #10</a>) > It is unclear how this is different from <a class="bz_bug_link bz_status_NEW " title="NEW - support for hancom hanword (.hwp) file" href="show_bug.cgi?id=108848">tdf#108848</a> that you mention. > > Just as in the latter, you note that "hwp" files (that are proprietary > binary format in a "compound" file) are not read by LO. Have you found a > documentation for it, like MS has created for its DOC [1], or do you offer a > sponsorship to fund the reverse engineering? > > You confirm that "cell" files (that are simply renamed XLSX) and "show" > files (that are renamed PPTX) are opened in LO. Of course, we have issues > related to XLSX (<a class="bz_bug_link bz_status_NEW " title="NEW - [META] XLSX (OOXML) bug tracker" href="show_bug.cgi?id=108897">tdf#108897</a>) and PPTX (<a class="bz_bug_link bz_status_NEW " title="NEW - [META] PPTX (OOXML) bug tracker" href="show_bug.cgi?id=108226">tdf#108226</a>) support. Is your request > "to fix all those bugs (and also all unknown)"? Do you realize that full > compatibility is not possible even in theory, because the two suites are > built on different principles/document models; and that even where > compatibility is possible, bugs happen, and need to be filed and fixed > one-by-one? > > [1] > <a href="https://docs.microsoft.com/en-us/openspecs/office_file_formats/ms-doc/">https://docs.microsoft.com/en-us/openspecs/office_file_formats/ms-doc/</a> > ccd7b486-7881-484c-a137-51170af7cc22 #1 It is unclear how this is different from <a class="bz_bug_link bz_status_NEW " title="NEW - support for hancom hanword (.hwp) file" href="show_bug.cgi?id=108848">tdf#108848</a> that you mention. >> I thought it was common with <a class="bz_bug_link bz_status_NEW " title="NEW - support for hancom hanword (.hwp) file" href="show_bug.cgi?id=108848">tdf#108848</a> to request support for the hwp file. <a class="bz_bug_link bz_status_NEW " title="NEW - support for hancom hanword (.hwp) file" href="show_bug.cgi?id=108848">tdf#108848</a> was a problem on the android platform and I mentioned it because I thought it was an extended request from Android to PC because it was a difference in the problem on the PC platform. #2 Just as in the latter, you note that "hwp" files (that are proprietary binary format in a "compound" file) are not read by LO. Have you found a documentation for it, like MS has created for its DOC [1], or do you offer a sponsorship to fund the reverse engineering? >> <a href="https://www.hancom.com/etc/hwpDownload.do">https://www.hancom.com/etc/hwpDownload.do</a> As a result of searching on Hancom's website, Hancom released its own HWP file format on June 29, 2010. Let me translate the first paragraph in the page. Hancom unveiled its binary format, HWP, and its markup language, HWPML, on June 29, 2010. We have released the previous versions of HWP 2.x/3x and HWP 2002 through HWP 2014 and HWP 2018. In addition, in October 2014, we released document, formula, and chart specifications for supplementation and distribution of HWP 5.0 specs. Using the File Type Disclosure Information document, anyone can create a variety of secondary works. OWPML, an open document format for HWP, is supported by the ".owpml" extension from HWP 2018 and the subversion is supported with the ".hwpx" extension from HWP 2010. The hwp file formatting guide is written in Korean, but no English-language document was found. I also translated the last paragraph. Hancom strongly supports the openness and standardization of document formats. Hancom has supported HWP 97 free of charge and has also released document formats for HWPML, the XML format for HWP 2002-2010 documents. Actively take part in the ethics committee associated with an open document standards and code worked for the standardization and openness of the file type. In addition, long-term retention of records in the ' Hancom Office ' standard format, pdf a the document format, international support and iso odf and actively storing files types of importing and ooxml.I desire.! Anyone who wishes to access this document will be provided to anyone who wishes to access this document, and any person who wishes to use the copy, distribution, publication and the content contained in this document in addition to viewing this document must fully recognize and agree to this copyright by Hancom. The distribution is the original unmodified all content be limited to the original or copies. The original and copy must contain the latest version of Hancom's specifications. Hancom may also actively exercise its rights against those who wish to acquire another exclusive and exclusive right based on the results obtained under the HWP Document File (.hwp) disclosure document and exercise it against Hancom. And this document, developed and the references listed in this document all copyright is the result of product development will be in an individual or group. However, "This product has been developed by referring to Hancom's HWP document file (.hwp) disclosure document," which must be written in all user interfaces, manuals, help, and sources within the product and only in the absence of such components. Hancom does not warrant any accuracy or integrity of the individual or group product developed by reference to this document and the information contained in this document. In conclusion, I felt strongly that Libreoffice needed a Korean developer. I'm not a professional developer yet. #3 You confirm that "cell" files (that are simply renamed XLSX) and "show" files (that are renamed PPTX) are opened in LO. Of course, we have issues related to XLSX (<a class="bz_bug_link bz_status_NEW " title="NEW - [META] XLSX (OOXML) bug tracker" href="show_bug.cgi?id=108897">tdf#108897</a>) and PPTX (<a class="bz_bug_link bz_status_NEW " title="NEW - [META] PPTX (OOXML) bug tracker" href="show_bug.cgi?id=108226">tdf#108226</a>) support. Is your request "to fix all those bugs (and also all unknown)"? Do you realize that full compatibility is not possible even in theory, because the two suites are built on different principles/document models; and that even where compatibility is possible, bugs happen, and need to be filed and fixed one-by-one? >> As a result of changing the names of the two files, they appear to be the same. I requested there's only normal, just in case it was submitted in support of the weight of the file hwp in files held by the contents of the differences a bit.Spoke with confidence that I can fix the problem. Normal, which will be held in files as you said a small problem is considered an unreasonable request of you. It may need to be modified on the PC platform as a support request from LO Writer in HWP format. P.S. I'm sorry that you might not fully understand my answer because I answered with a translator.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>