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:
but the actionType seems to workCode: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
-
Thank you very much.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
-
Hello, just bumping this up to know if I should actually make a version of my tutorial for each locale or if I'm missing some other option.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
-
Hello, I've actually tried like this: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).
and then I've tried to load it like this (as I don't think it could work with Tour.loadTour()):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> ....
and, while I see the same key correctly used in the js version of the ds, in the js version of the Tour I see the <fmt> tag in the title. Am I missing something?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>
Thanks for the suggestion, I actually hadn't thought of that, but it will definitely work. However, does this have any implications on the features, or is it fully equivalent?Originally posted by Isomorphic View PostIf you instead define them in JavaScript, then you use the usual client-side approaches.
Comment
-
Hi Claudio
Sorry for the long pause on this.
We've made a change to have the server pick up the appropriate messages from the resource bundle file and substitute them in for tour *.proc.xml files.
Please try the next nightly build (Nov 27 or above) in the 13.1 / 14.0 branch to see this in action.
Let us know if it doesn't work for you
Regards
Isomorphic Software
Comment
-
SmartClient Version: v13.1p_2024-12-01/Enterprise Deployment (built 2024-12-01)
Hello, it doesn't seem to work for me, I still see the <fmt> tags in the js-translated Tour.
Thanks for the suggestion, I actually hadn't thought of that, but it will definitely work. However, does this have any implications on the features, or is it fully equivalent?Originally posted by Isomorphic View PostIf you instead define them in JavaScript, then you use the usual client-side approaches.
could you also please comment on this?Originally posted by claudiobosticco View PostThanks for the suggestion, I actually hadn't thought of that, but it will definitely work. However, does this have any implications on the features, or is it fully equivalent?
Comment
Comment