Skip to main content
June 23, 2015
解決済み

New import procedures re-generating image folders it's not allowing us to rename the folders.

  • June 23, 2015
  • 返信数 1.
  • 457 ビュー

Hey guys any suggestions in solving the following issue?

An ongoing issue with RoboHelp has always been our project names being too long to migrate. We can manually reduce the size of folder names and topic file names, however, with the new import procedures, RoboHelp is generating image folders separate from the topic files and we are unable to rename these folders. This negates the efforts we have made to reduce the file names of the topics. When we attempt to rename the folders, RoboHelp re-creates the original folder and the image no longer appears in the Project Manager pod or in the published HTML files.

Any kind of help is greatly appreciated.

Thank You.

このトピックへの返信は締め切られました。
解決に役立った回答 Captiv8r

Yes, Rick they appear the same as they would do in RoboHelp. Do you have something on mind?

Peter, thanks for sharing some insight! I believe I did understand his point. I am quiet new to RoboHelp in general so I can't exactly confirm which one of us is misunderstanding..

Kind regards,

Thanks again guys!

- Haider


Hello again

Okay, so I really just wanted you to understand that what you are seeing inside RoboHelp is nothing RoboHelp is doing to change anything. Now let's talk a bit about this document. One thing I would suggest (and my esteemed colleague Peter suggested) is that you rename this document prior to importing it into RoboHelp. Short file names will lead to short paths (and fewer possible issues) once we enter the RoboHelp universe.

When working with something like RoboHelp, you have all sorts of different files involved that help track your project. I notice that your Word document is using a comma in the file name. I'd strongly suggest avoiding any characters other than 0-9, a-z, A-Z and the underscore ( _ ). Any character other than those is to be considered "special" and will only cause you grief at some future point.

So as you have seen, when Word creates HTML, it also creates these folders. RoboHelp does its best to have your back and prevent you from shooting yourself in the foot. I noticed when I tested by saving as HTML, that more than simple images were placed in that folder Word created. RoboHelp is likely preventing you from changing the name of the folder because of the other files inside. Generally speaking, RoboHelp allows you to name your images as you wish and store them anywhere you like. But this content is a bit special, as it comes from Word.

One way to work past this would be to save your images separately from Word, naming them appropriately, then importing a Word document without the image. Then add the images later. That way you shouldn't end up with the unwanted folders and the images may be stored where you want.

Cheers... Rick

返信数 1

Captiv8r
Legend
June 23, 2015

Hi there

Can you share a screen capture of the section of RoboHelp where you are unable to rename folders? I have a sneaking suspicion I know what is happening, but before I babble on, I'd like to see it.

Thanks... Rick

June 23, 2015

Thanks for showing interest Rick,

Here is the screenshot.

Thanks again for the help!

- Haider

Captiv8r
Legend
June 23, 2015

Ahhh, okay


So it appears you are using content created by importing from Microsoft Word?


I'm unaware of anything "new" RoboHelp would be doing here. The folder names you get are based off the names the Microsoft Word document was using. I believe you would see the same naming and result if you took these Word documents and saved them as HTML.


One way to make the names a bit shorter is to ensure the document file names are short before you import them into RoboHelp. As for the names of the folders containing the image files and other assets, I believe those are actually created by Word during the process. Likely, you can't simply rename them because of embedded code in the documents and associated files that is pointing to these folders.


Maybe consider filing a bug with Adobe so they can look into doing what they can on their side to smooth things out. But that would only apply to future versions.


Click here to file a bug


Cheers... Rick