Hello, I'm trying the Tour module and I've noticed that the step titles aren't internationalized.
Announcement
Collapse
No announcement yet.
X
-
Also, I'm getting this WARN:
Code:2024-05-14T16:40:47,445 WARN Validation Validation errors validating a 'Tour': { "/Tour[@ID=profileMenuTour]/steps/3/TourStep":{ recordPath:"/Tour[@ID=profileMenuTour]/steps/3/TourStep", actionType:{ severity:"ERROR", errorMessage:"Must be in set [click, doubleClick, mouseOver, drag, change, none, any] but is menuItemOpen." } } }
-
hi Claudio,
We've added around 40 new framework i18n attributes for all hard-coded strings in the Tour subsystem, and you'll find them already in the language packs with AI translations as of tomorrow's builds, dated May 29 and later.
Another 60 or so i18n attributes unrelated to Tours were picked up and translated at the same time, including the max grouping messages you mentioned in another thread.
We're taking a look at the warning you see and will update here shortly.
Comment
-
Originally posted by Isomorphic View Posthi Claudio,
We've added around 40 new framework i18n attributes for all hard-coded strings in the Tour subsystem, and you'll find them already in the language packs with AI translations as of tomorrow's builds, dated May 29 and later.
Another 60 or so i18n attributes unrelated to Tours were picked up and translated at the same time, including the max grouping messages you mentioned in another thread.
We're taking a look at the warning you see and will update here shortly.
Actually in post #3 I meant also to ask if it's possible to internationalize what I write in the <instructions> tags and in the title attributes in my tour.proc.xml file, as I tried an approach similar to that used for dataSources but it didn't work
Comment
-
Originally posted by claudiobosticco View PostActually in post #3 I meant also to ask if it's possible to internationalize what I write in the <instructions> tags and in the title attributes in my tour.proc.xml file, as I tried an approach similar to that used for dataSources but it didn't work
Comment
-
claudiobosticco sorry we missed that question. If the Tour is defined in XML, you should be able to use the same i18n mechanisms that apply to DataSource .ds.xml files and screens (.ui.xml files).
If you instead define them in JavaScript, then you use the usual client-side approaches.
MQDeveloper - we have a prototype of a Tour-recording system. If you are interested in Feature Sponsorship to make it an officially supported feature, start here!
Comment
-
Originally posted by Isomorphic View Postclaudiobosticco sorry we missed that question. If the Tour is defined in XML, you should be able to use the same i18n mechanisms that apply to DataSource .ds.xml files and screens (.ui.xml files).
Code:<Tour ID="firstTour" showProgress="true" xmlns:fmt="WEB-INF/"> <fmt:bundle basename="i18nMessages" encoding="utf-8"/> <steps> <TourStep ID="welcome"> <title><fmt:message key="welcome"/></title> ....
Code:<script type="text/javascript" charset="UTF-8"> <isomorphic:XML> <jsp:include page="/WEB-INF/ds/profileMenuTour.proc.xml"/> <jsp:include page="/WEB-INF/ds/aSampleDS.ds.xml"/> </isomorphic:XML>
Originally posted by Isomorphic View PostIf you instead define them in JavaScript, then you use the usual client-side approaches.
Comment
Comment