Skip to content
This repository has been archived by the owner on Feb 26, 2022. It is now read-only.

History / HTML Page Localization

Revisions

  • The `data-l10n` proposal is usefull. We can just put `data-l10n-id` and keep this existing node content if we do not have a property file for the current locale.

    @ochameau ochameau committed Mar 27, 2012
    5ee151f

  • Introduce DOM Localization

    @ochameau ochameau committed Mar 26, 2012
    18fb527

  • keys can be localized strings, supporting gettext-style localization

    @mykmelez mykmelez committed Dec 30, 2011
    0cd9118

  • describe alternative to explicit key specification

    @mykmelez mykmelez committed Dec 30, 2011
    f3c672c

  • clarify distinction between Dynamic Localization of Text and Dynamic Localization of HTML

    @mykmelez mykmelez committed Dec 30, 2011
    9ec89a8

  • note possibility of making localization processing disablable

    @mykmelez mykmelez committed Dec 30, 2011
    befca4b

  • Updated HTML Page Localization (markdown)

    @mykmelez mykmelez committed Dec 28, 2011
    32b3559

  • integrate localization processing into addon:// protocol handler, removing need to implement content sniffer/stream converter

    @mykmelez mykmelez committed Dec 28, 2011
    150c3e8

  • initial draft

    @mykmelez mykmelez committed Dec 21, 2011
    0c27669