[claudiobosticco]

SmartClient Version: v13.1p_2024-12-19/Enterprise Deployment (built 2024-12-19)

Hello, any news about this issue? I still see the <fmt> tag in the js-translated Tour, with the approach described in post #11

[claudiobosticco]

Hello, aside from the issue with the <fmt> tags, could you please provide your thoughts on this question from post #11:

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?

I’m considering switching to the JS version if there aren’t any drawbacks.

[Isomorphic]

Hi Claudio
Sorry for the long silence on this. We did some preliminary work here and thought we had things working but clearly that's not what you're finding.
A proper in-depth investigation has been queued up for a while behind some other priorities. Our dev team anticipates getting into this over the next few work days so should have more information for you soon.

Regards

Isomorphic Software

[Isomorphic]

We set up a test based on the Showcase Tour sample, https://smartclient.com/smartclient/...id=productTour. We then modified the following line in the productTour.proc.xml file to add the <fmt:message> tag:

<instructions>Welcome to the SmartClient Showcase!  We'll show you how to use it.  <fmt:message key="instructions1"/></instructions>

Then we created a productTour.properties file immediately under WEB-INF/classes and defined an "instructions1" property:

instructions1: Extra instructions in English

This does work - the <fmt:message> tag is replaced in that Welcome message with "Extra instructions in English". So we think this is fundamentally working. If it is not working for you, please can you provide more information about the exact steps you have taken

[claudiobosticco]

Hello, thanks, I got it working, but I need to specify the bundle in the <fmt:message> tag (while in the datasources I only use <fmt:bundle basename="...). I'll try to understand If I could use the more compact notation I use in the datasources.

Regarding the JS version, are there any limitations for Tours?
I ask because with the <fmt> tag I lose the ability to load the Tours dynamically, whereas in JavaScript I could continue doing so.

[claudiobosticco]

Hi, I wanted one more comment on the differences between the JS and XML modes for Tours.

Basically, if I use XML and therefore internationalize the messages the same way I do for XML dataSources, it works, but I have to load the files statically (that is, I can’t use isc.Tour.loadTour(), and there is no equivalent of the dataSourceLoader for Tours).

At this point I would prefer to use the JavaScript version of Tours, but I wanted confirmation that there are no limitations compared to the XML version.

[Isomorphic]

The XML format of Tour is just converted to the JavaScript format before being run. So the only thing you can possibly be missing are things associated with that transform, like using server-based i18n, as you pointed out. Also, you could use XML-centric tools to validate the format, but these days, the JSON-based tools are better.