Coming Soon
...
The internationalisation has the following arguments when set up:
- the appliesToType argument which is a function from Type to bool where the type is a container type and the result is true if this container type is cached.
- the localRouteKey argument which contains the name of the route key which contains the locale indicator: this must be specified on any route to multi-locale content.
- the defaultLocale argument which specifies which is the default locale
- the localeDict argument which is a Dictionary<string, string> of the possible locale codes as keys against the friendly names of the locales.
...
Other useful procedures can be done using the filter page with a little thought. For example, to find content items which have not been modified since they were copied to a locale version (and so still need translation) use the Created When and Updated When filters, setting both Show checkboxes to true. You can then inspect the created and updated dates of the items and if these are the same, they will not have been edited.
While working in the content editor, setting up the module will add a new version changer to allow you to switch between language versions:
Adding the Internationalisation module to a Site with Existing Content
...
- The built in Resource Files system in .Net
- Adding content properties for these headings etc and using
PropertyRedirectAttributeto to make these properties shared across all content items of the same type and the same locale version (see Sharing and Combining Content Data) - Using the Dictionary system which comes with the Internationalisation module
...
The third option is in our view the easiest to work with. Adding the Internationalisation module adds a UI for creating a content item type called TranslationDictionaryEntry. This list/detail editor can be accessed at /Lynicon/Dictionary or via the Dictionary button which the I18n module adds to the navigation bar at the bottom in editing mode.
