There are different options that are available for you as a Mashup developer. You can create resource files relative to the mashup project, or you can use M3 constants or you can reuse constants available in Lawson Smart Office.

To add language files to the project do the following. Create a folder named “Localization” and in that folder you create one xml file per language that you would like to support. The xml file should be named to the language code. Start by adding en-us.xml. You add it to the Mashup project by selecting “Add resource” and point to the en-us.xml file.

The xml content should look similar to this:

<?xml version="1.0" encoding="utf-8" ?>
<assembly name="CurrencyConverter">
  <area name="Convert Tab">
    <entry name="Convert" type="Header" comment="">Convert</entry>
    <entry name="About" type="Menu" comment="">About...</entry>
    <entry name="Refresh" type="Menu" comment="">Refresh</entry>
  </area>
  <area name="Rates Tab">
    <entry name="Rates" type="Header" comment="">Rates</entry>
    <entry name="ConvertAmount" type="Label" comment="">Convert this amount:</entry>
  </area>
</assembly>

There can be many areas but the name still has to be unique in the file since the name is what will be used as a key.

Lawson Smart Office currently supports the following languages: cs, da, de, el, en-US, es, fi, fr, hu, it, ja, nl, no, pl, pt, ru, sv, zh-CN.

To use the constants use the markup extension Constant. The mashup namespace is already declared so the value for the Content (or Text, Heading depending on control) is what you need to add.

<Label Content="{mashup:Constant CurrencyWidgetDescription}" />

You can read more about the Constant Extension in the Mashup SDK documentation found in the Designer.

Once the above steps are completed your mashup project will look like this:

Lawson Smart Office uses similar XML resource files for it’s constants. They are divided into one resource file per assembly. Each file corresponds to a generated language file with static fields. You can use these constants as well. The constants that are available are documented in the LSOSDK.chm which is delivered in the SDK pack (not the documentation that is in the mashup designer). The documentation that is in the mashup designer is MashupSDK.chm and this file is also available in the SDK pack.

For the Mango.UI assembly the language class is named LangUI.

For Mango.Core the language name is LangCore. For MForms the language class is Lang in the MForms namespace. Use the SDK documentation to browse and search for available constants. You use the constant as you would use any static reference in xaml.

<Label Content="{x:Static lang:LangUI.Related}" />

NOTE! In the example above you need to declare the “lang” namespace to your Mashup Grid.

<Grid xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:lang="clr-namespace:Mango.UI;assembly=Mango.UI" xmlns:ui="clr-namespace:Mango.UI.Controls;assembly=Mango.UI" xmlns:mashup="clr-namespace:Mango.UI.Services.Mashup;assembly=Mango.UI">
</Grid>

A third alternative would be to use language constants for M3. Language constants are available in MVXCON or in MVXMSG, in order to know which constants are avalailable you need to use the MAK tools for M3. For MIDetail panenels we have the option of generating the mashup with these constants. You need to know the name of the constant and which file it belongs to. The syntax is as follows:

<Label Content="{m3:Constant Key=WCU0215,File=MVXCON}" />

The M3 markup extention will use the M3 language from MNS150.

The complete example is available here.

Some final notes:
You need to restart LSO if you change language files becuase they are cached.
The language culture name is taken internally from the LSO (client) language, NOT the language of the M3 User.