Using the LPManager
Install as regular module and instantiate on a page of your site. Note two new permissions are created: Manage Permissions and Manage Objects.
The module settings also reveal the DNN 5 pack settings:
Before we go anywhere we need objects to manage
Either add objects that are already installed, or add them by uploading. Note you should only add higher versions for those that you already installed.
Now we are going to manage who can do what
You can add either 2 letter codes for locale or 2-2 codes. Note the username textbox is autosensing and will suggest usernames that match.
The user that has particular edit permission will see the relevant links on the module:
Here the user can edit nl-BE. Clicking on this will bring up the following screen:
The block at the top shows the state of this pack. The version dropdown shows all versions of that module that are in the system. The selection dropdown is used to make a selection on which texts the user would like to edit. The source locale is useful for those doing a specific translation (like nl-BE). They can bring up not only the original texts, but also the texts from the generic language for instance.
Now we click ‘Edit Pack’ to bring up the edit screen.
The translations are grouped under their resource file heading. These can be opened as collapsed. Clicking Translate All or the magic wand icon will start translating via Google translate. Transfer will put the original text into the translated text box for further editing. This can be useful when translating HTML and you want to import the HTML structure first.
Click OK to save the translations.
Finally the user can download the language pack of their choice. They are directed to either the module or a fixed aspx that is also part of the module: DesktopModules\DNNEurope\LocalizationEditor\RequestPack.aspx. The querystring parameters will load up the form correctly.
Either they opt to download directly the specific pack, or they type in their locale and download this through ‘Get Pack’. This then redirects to the pack page: DesktopModules\DNNEurope\LocalizationEditor\Pack.aspx. Again the querystring parameters inform the module what to do. As you can see this means you could integrate the module into a more sophisticated download matrix and directly call this page to provoke downloads.