Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

-- Tim
225 Janice Drive
Athens, GA 30606-1638
home: 706-543-0592
cell: 706-248-6544
fax: 888-415-5991
I know the plans I have for you:
Plans to prosper you and not to harm you;
Plans to give you hope and a future.
               --- God (Jeremiah 29:11)

On 10/28/2013 11:04 PM, Thomas Blasejewicz wrote:
(2013/10/29 2:06), Tim Deaton wrote:
Did you zip up the html file and the subdirectory containing the images as one operation? And did your settings also save the relative path of the subdirectory?

If you zipped the html file, and then went to the subdirectory and zipped the files there (even into the same zip file), the zip file would then not have the relative relationship info needed. The same failure would happen if you zipped it all at once, but had the setting to save the relative path turned off.

-- Tim

On 10/28/2013 8:31 AM, Jay Lozier wrote:
On Mon, 2013-10-28 at 18:58 +0900, Thomas Blasejewicz wrote:
Good evening from Japan
Maybe I did ask a similar question before ...

I wrote a book using Writer which I am now trying to upload to Kindle.

The instructions say, I must save the file as html and then create a zip
file from the html file + the images.
"Save as ... html" creates a content file and a whole long list of files
for the images.

I would contact Amazon technical support and ask what is the problem. It
appears that they want the images in the same directory as the html
files. If so, it is relatively easy to correct the html file references
to the images, if a bit tedious, and move the images into the same
folder. LO actual exports html in the preferred mode with the images
stored in separate folder.

Thank you.
I am afraid, I am not following you.
"save the relative path of the subdirectory" ...
Where and how am I supposed to do that.
This morning I tried to
* save the Writer file as html
* copy the created/indexed image files into a separate folder (like the "Word procedure")
* zipped both.
But nowhere I can see any setting/check boxes etc. (including options -> paths) where I can set a relative path ...
And the uploaded zip file again gives the same error.
So does the zip file created with Word for that matter.

First of all, I am no expert. I have not (until just now) tried saving an odt document as an html document, and it has been a decade since I tried it (in a class) with MS Word. But I have saved web pages to my hard drive, including backup copies of the code of my own website generated by my wysiwyg editor.

In all that saved code (including from the 2002 class using MS Word), the basic structure I see is a file with the .html extension and a subdirectory with the same name - except that the ".html" is replaced with "_files". Inside that subdirectory are all the other files (gif, jpg, css, ..) that are part of that webpage. So the result looks something like this:
\website_test          <-parent directory
    test_page_files     <-subdirectory with files used by the .html file
    test_page.html     <-html file

To archive that into a .zip file, you open your archive program, go to the "\website_test" directory, and add both the .html file and the subdirectory into the .zip file. (Older archiving programs I've used gave you the option of whether to remember the relative directory structure or not. That's why I asked about the settings. The program I currently use - 7zip - doesn't appear to give you a choice; it always remembers the directory structure, which is what you want.)

When you look at the .html file with a text editor, you see all the code. If the .html uses a picture file called sample.jpg, then somewhere in that code you will see a reference that looks something like this: <IMG SRC="test_page_files/sample.jpg" NAME="graphics1" ALIGN=LEFT WIDTH=350 HEIGHT=350 BORDER=0><BR CLEAR=LEFT><BR>

HOWEVER, based on the test I did when starting this reply, LO Writer appears to do things somewhat differently.

I opened an existing .odt file, added a picture to it, and used "save as" to save it to "test_page.odt". Then I used "save as" again to save it to "test_page.html". It DID NOT create the structure I've always seen elsewhere and which I outlined above. First, when you open the file in your browser, the formatting will not look the same as it did in LO. Second (a minor point), the .jpg gets a random 8-digit name instead of keeping the name of the original picture. But more importantly, the picture is NOT stored in a sub-directory. Instead, the name of the .html file (with underscores replacing the extension dot and trailing the "html") is appended to the beginning of the .jpg name, and the .jpg file is stored in the SAME directory as the .html file. Finally, the picture is referenced in the .html file as shown here: <IMG SRC="test_page_html_m6869e14e.jpg" NAME="graphics1" ALIGN=LEFT WIDTH=350 HEIGHT=350 BORDER=0><BR CLEAR=LEFT><BR>

This change in file structure is most likely what Amazon was having trouble with.

As to fixing the problem I see: After saving the file as an .html file, I would try to do this: 1. Create a new parent directory to work in, and copy your "test_page.html" file into it. 1. Create a subdirectory called "test_page_files" to match the "test_page.html" file.
2. Copy all those "test_page_html_*.* files into that subdirectory.
3. Rename all those files in that subdirectory by removing the "test_page_html_" from the filenames. 4. Open the .html file in a good text editor. I use the free "NoteTab Light", which runs in Windows. 5. Use Find/Replace to replace all instances of "test_page_html_" with "test_page_files/". 6. Save the result, then double-click on the .html file to verify that it opens in your browser and is accurate.

If the results are acceptable, then zip it up, re-submit it and see if they like it now. If not, then you need advice from someone who knows more than I do.

I hope this helps.
-- Tim

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.