file naming conventions

Hi Ashley,

I ssaw you replied to a thread about file names - Could you confirm something for me please?

From thread:

http://community.articulate.com/forums/t/22076.aspx 

Karen said:

"I changed the file name of the attached PDF to exclude underscores, numbers" 

Julie said:

I was having the exact same error and I used your suggestion to fix the issue. My file name was too long. After I shortened the name and re-attached it to the resources, it opens without error. Thanks for the help. 

...and I seem to remember seeing a link to:

http://www.articulate.com/support/storyline/create-edit-and-publish-articulate-storyline-courses-on-your-local-hard-drive

Where it says:

Avoid using special characters, accents, or symbols in your file paths and file names. Learn more about naming conventions in this Microsoft article. 

For the last 20 years I have been using underscores and alphanumerics including 0 thru 9 but avoiding other 'special' characters.

The Microsoft article says:

Use any character in the current code page for a name, including Unicode characters and characters in the extended character set (128–255), except for the following:

The following reserved characters:
< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk) 

Are you  saying that there could be issues with file name length, using underscores, or  using numerics with filenames in storyline?

Thanks.

Karl

7 Replies
Ashley Terwilliger

Hi Karl,

File name and file path length is always going to be an issue if you exceed the 260 character limit, which is a limit imposed by Microsoft Windows. (Publishing adds characters to the file path you selected. If it exceeds 260 characters, your published output will be incomplete.)

The rest of what you're referring to comes from this Microsoft Article, and you can use underscores (I do regularly in place of spaces - which I think was part of Karen's issue if you look at her file path you'll see the % symbol added) and numerics but I would use any symbols, accented letters, etc. For example I saw a course that had a file path similar to "Course name.En.story" and the space and the extra period cause issues with the course. 

Do you have a course with an unusual file name that is causing difficulty? I'd suggest trying to rename the file to see if that helps at all. 

Karl Gunter

Ashley Terwilliger said:

Do you have a course with an unusual file name that is causing difficulty? I'd suggest trying to rename the file to see if that helps at all.


No, what threw me was when she said that it worked when she excluded underscores. I've never had a problem with that sort of thing and prefer to use underscores rather than spaces for files that are going online (i.e. better readability and no % signs added to file names).

As for the file path length - Microsoft really should have sorted that out by now!

Just thought I'd better check just in case.

Thanks

Nita  Venter

Ashley Terwilliger said:

Tell Microsoft that.  

As for file names, everyone has their own style...for me, I often won't use spaces or underscores, but instead label courses like "ThisIsMyStorylineCourseName.story"  

To each their own.  


Ashely, just to clarify. You change/rename the folder name that Storyline creates based on the course title to one that has no spaces?

Ashley Terwilliger

Hi Nita,

I save my .story files as such, and then when I go to publish my course I can also change the published output folder name or adjust the title within the publish window settings (less desirable as it's typically public facing somewhere such as in your LMS). I generally do it as when I load it into my webserver if there are spaces (instead of underscores) those are treated as % when I look at the link in my web server which is messier looking. You don't need to set your files up as such though - just avoid the special characters, diacritical marks and accents and you should be ok. 

Nita  Venter

Ashley Terwilliger said:

Hi Nita,

I save my .story files as such, and then when I go to publish my course I can also change the published output folder name or adjust the title within the publish window settings (less desirable as it's typically public facing somewhere such as in your LMS). I generally do it as when I load it into my webserver if there are spaces (instead of underscores) those are treated as % when I look at the link in my web server which is messier looking. You don't need to set your files up as such though - just avoid the special characters, diacritical marks and accents and you should be ok. 


Thanks Ashley, i was concerned that i would "break" the course if I changed the output folder name or lose my audio as i had done in the past with Presenter.  'N