Loading...

Localizing warning messages

Localizing warning messages

Home Forums QuickApps Forum Localizing warning messages

  • This topic is empty.
Viewing 4 reply threads
  • Author
    Posts
    • #5041
      Anonymous
      Anonymous
      Participant

      Hi

      Can we get help with this?

    • #5694
      Anonymous
      Anonymous
      Participant

      Hi Kate,

      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\4.0.0.0__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.

    • #5693
      Anonymous
      Anonymous
      Participant

      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?

    • #4230
      Anonymous
      Anonymous
      Participant

      Hi QWP experts,

      Could you please help with the following question:

      Warning Messages displayed in English instead of Spanish for Spanish site.

      localization warning.PNG

      Can it be localized?

      Thanks,

      Kate

    • #5692
      Anonymous
      Anonymous
      Participant

      Hi Siddardha,

      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.

Viewing 4 reply threads

You must be logged in to reply to this topic.