Talk:Writing localizable code

From MDC

There are a few pages on the old waste-dump we call the "MLP web pages" that talk about XUL L12y and guidelines for localizeable code, all written by the former Netscape/Mozilla L10n owner, Tao Cheng:

• XUL Localizability issues - this is of historic value, written back when XUL wasn't localizable, discussing how that problem could be solved at all
• Making XUL Localizable - this was written once they had settled on a solution on how to achieve L12y of XUL at all
• Markup Languages Style Guidelines - describes a "good coding style for markup languages including XML, XUL, HTML, and XHTML"
• Writing Global Customization Friendly Code - describes how to "write localization (l10n), customization, and internationalization (i18n) friendly code"

--KaiRo 09:18, 14 February 2006 (PST)

Add a blurb about accesskeys and commandkeys, like

Be consistent with shortcuts and accelerators key naming 

Often you will define a key for a UI element (ie. the label for a button, a checkbox or a menu option) that can be accessed with a keyboard accelerator (ie. 'Paste' menu option inside the Edit menu has 'P' accelerator) or a shortcut (ie. Edit -> Paste can be executed by pressing [Ctrl]+[V]). Try to be consistent when naming the entities for a label and its associated accelerator ("accesskey") and shortcut

("commandkey"). Example:

<! ENTITY editpaste.label "Paste" >
<! ENTITY editpaste.accesskey "P" >
<! ENTITY editpaste.commandkey "V" >

(per ricardo)

--AxelHecht 10:26, 20 February 2006 (PST)