Our LMS imports the Course Title and Description from the imsmanifest.xml file. The issue is that this file replaces all accented characters with a question mark. The result is that when the course is imported to the LMS, the course name and description carry across these question marks which causes a huge issue since we cannot edit the course name and description fields. Is there a "simple" fix for this? The frustrating part is that the course name and description look fine in SL2 publish screens.
Really strange. You might consider submitting a trouble report. This doesn't seem normal and could be a bug. In the mean time, I replaced all of the ?n instances with ón in the attached with a search and replace. Guessing these are all ó but I could be wrong.
@Steve Flowers -- thanks, I ended up modifying that imsmanifest file in DreamWeaver for the two Spanish courses we are testing (that process is going to have to be repeated 250+ times). I figured if anyone had a fix it would be you. You do a great service on these boards and I've often used your solutions.
@Steve Gannon -- thanks for the reference to the known issue. Kinda sucks for me though because we are migrating approximately 250 courses to our new LMS and not only are we re-publishing them, that means now having to open each imsmanifest file and manually changing all affected characters.
Hopefully this is something that can be fixed as an update or a x.x.1 or something because for such amazing language support within the program, seems inconsistent to drop the ball on the created xml file without some sort of resolution. Especially when these characters display just fin in the Publish screens. All the courses we are migrating are Italian, French, Turkish, Spanish, German and Portuguese--full of special characters.
I've also added this thread to the existing report filed with our QA team so that they're aware of how many users have encountered this issue. I'll be able to update this thread when there is additional information to share.
Just curious if there is any progress on this. As I search the "archives" of these boards, it seems the same thing was an issue with SL1 waaaay back when it first launched.
I don't have any updates to share in regards to this issue yet, but it's still with our QA team for additional review. Once we have information to share we'll post here for you and others who are following along with this thread.
6 Replies
Hey Jeffrey -
Really strange. You might consider submitting a trouble report. This doesn't seem normal and could be a bug. In the mean time, I replaced all of the ?n instances with ón in the attached with a search and replace. Guessing these are all ó but I could be wrong.
This is a known issue:
http://www.articulate.com/support/storyline-2/non-english-characters-in-course-title-display-as-question-marks-in-lms-sl2
@Steve Flowers -- thanks, I ended up modifying that imsmanifest file in DreamWeaver for the two Spanish courses we are testing (that process is going to have to be repeated 250+ times). I figured if anyone had a fix it would be you. You do a great service on these boards and I've often used your solutions.
@Steve Gannon -- thanks for the reference to the known issue. Kinda sucks for me though because we are migrating approximately 250 courses to our new LMS and not only are we re-publishing them, that means now having to open each imsmanifest file and manually changing all affected characters.
Hopefully this is something that can be fixed as an update or a x.x.1 or something because for such amazing language support within the program, seems inconsistent to drop the ball on the created xml file without some sort of resolution. Especially when these characters display just fin in the Publish screens. All the courses we are migrating are Italian, French, Turkish, Spanish, German and Portuguese--full of special characters.
Hi Jeffrey,
I've also added this thread to the existing report filed with our QA team so that they're aware of how many users have encountered this issue. I'll be able to update this thread when there is additional information to share.
Just curious if there is any progress on this. As I search the "archives" of these boards, it seems the same thing was an issue with SL1 waaaay back when it first launched.
Hi Jeffrey,
I don't have any updates to share in regards to this issue yet, but it's still with our QA team for additional review. Once we have information to share we'll post here for you and others who are following along with this thread.
This discussion is closed. You can start a new discussion or contact Articulate Support.