multilingual

  • Include an article based on the current language.

    To include either the "membermeeting" or the "ledenvergadering" article.
    {article[en-GB]Membermeeting}{text}{/article}{article[nl-NL]Ledenvergadering}{text}{/article}

  • Add different content, hard-coded, optionally formatted text, images for different languages. The replacement name {txt is somewhat unfourtunate.
    In this aproach we use "hard-coded" coded which is ok for unique situations. In other situations a more reusable aproach may be prefered, however that requires some more preparation, see language strings and test using language files

    Have the field populated by either the englisch or the dutch word for "beer".
    {txt[en-GB]}Beer{/txt}{txt[nl-NL]}Bier{/txt}

  • Link to an translated version of a web-page using Google

    Nu.nl is a dutch site, to have in an English context you would want to have it displayed in English ( however bad the translation )
    {link[nl-en]}http://www.nu.nl/{/link}

  • There are a number of dedicated extensions out there that do language related stuff. I found that a lot of them can be replaced by some common sense and a combination of NoNumbers extensions, most often the free ones will suffice.

  • In order to re-use translations for multiple extensions and or websites it makes little sense to use hard code translations. It makes more sense to centralize the translations in ini files and reuse them over and over again. Initially more labour intensive, it will pay-off eventually

    Insert language equivalent for 'beer'

    [ls[BEER]]

    Note the lack of the self imposed prefix BLOX42- this i omitted here for readability.

  • Language files are the Joomla standard mechanism to define translations. The are in an .ini file format. For details brush up on the laguage file documentation, it will tell you details on the format and location of the files.