I'm publishing a course for the web. It includes a quiz. The published files in the data folder include file names with special characters - SH0A7E~1.SWF. I would like to upload this course to SharePoint but SP does not accept these special characters. Is there a way to publish the quiz without these characters?
Methods for converting from FAT32 to NTFS will vary depending on your Operating System, so you'll want to check with your IT folks on that. In the long term, however, it seems likely that if you need to upload your content to SharePoint, you'll want to perform all Studio publishing (and uploading) from a PC that runs NTFS.
Please let us know if you need anything else, and have a great day!
Can you please share (a) your .quiz project file and (b) your zipped, published Web output within a private Support Case? This will allow us to attempt to reproduce the problem and determine a possible work-around. Thanks!
3 Replies
Good Afternoon, Jason.
If your installation of Windows uses the FAT32 File System, Microsoft mangles long filenames by taking the first six non-space characters in the filename and adding a tilde (~) and then a number to ensure the uniqueness of the filename on the disk. In addition, I've read that SharePoint does not allow you to use a tilde anywhere in a file name--ouch!
NTFS is highly preferred over FAT32, and this is how to check which format you're using.
Methods for converting from FAT32 to NTFS will vary depending on your Operating System, so you'll want to check with your IT folks on that. In the long term, however, it seems likely that if you need to upload your content to SharePoint, you'll want to perform all Studio publishing (and uploading) from a PC that runs NTFS.
Please let us know if you need anything else, and have a great day!
Justin,
Thank you for your response. My hard disk is already formatted using NTFS. It appears that something else is causing this issues. Any other ideas?
Thank you,
Jason
Hello again, Jason.
Can you please share (a) your .quiz project file and (b) your zipped, published Web output within a private Support Case? This will allow us to attempt to reproduce the problem and determine a possible work-around. Thanks!
This discussion is closed. You can start a new discussion or contact Articulate Support.