- This topic is empty.
- 11/15/2012 at 9:19 am #5041
Can we get help with this?
- 11/15/2012 at 10:40 am #5694
This type of messages can be translated but they're not fully localizable (can't display dynamically the message based on the current culture).
The scenario is the following, if you have a server/farm that serves employees that speak Spanish then you can translate the message and they'll see the message in Spanish.
To do that go on each WFE server in your farm, open the file WAListForm.js from the following location (this can be different based on your configuration)
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\wpresources\WA.ListForm\188.8.131.52__2b4b09f1c57c8f0b, localize the message and replace it with your new message.
The above can be applied on all js messages in the wpresources WA* and Quest* folders.
Please note that the users have to clear the browser's cache to see the change.
Before you do any change please backup these files.
I hope this helps. If you still have any questions please let me know.
- 11/19/2012 at 2:43 am #5693
With this solution the message will start appearing in Spanish even for english user. What if we are using the same farm for English and spanish sites?
- 11/29/2012 at 8:47 am #4230
Hi QWP experts,
Could you please help with the following question:
Warning Messages displayed in English instead of Spanish for Spanish site.
Can it be localized?
- 11/29/2012 at 8:47 am #5692
Unfortunately there are little options for translating these warning messages. In a load balanced environment there is no way to know which machine will serve the request. As a result the fix above is an "all or nothing" approach. The language packs do not translate warning messages and as a result leave little room for alternate solutions.
You must be logged in to reply to this topic.