From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

Note: Generally, the structure of the portal revolves around pagenames and templates based on pagenames. Therefore, be super careful when changing the name for any page and when naming a page.

Main portal pages[edit]




Templates within the proposal form template[edit]



Templates within the progress report form template[edit]


Letters of intent[edit]

Discussion pages[edit]

Report pages[edit]

Committee pages[edit]

Example pages[edit]

Key templates[edit]


See FDC portal/Comments#Translation of FDC pages for discussion about the translation framework.

The translation of the FDC pages can be achieved with the Translate extension activated on Meta; see Meta:Babylon for the translation portal on Meta.


Given there are a lot of templates on the FDC pages, each template should be translated independently with the Translate extension; and they should be included in the pages with {{Translatable template|TheTemplate}} to be displayed in the correct page language.


Dates can be automatically translated in the page language by writing {{#time|j F Y|2013-11-08}} in the original page (see #time for more details). With this system, the dates are always consistent accross languages.

  • Dates used in templates for computing expressions should also use {{#time|format|date}}</nowiki> only with formats using the xn flag before each numeric date elements, otherwise the returned value will not be computable when their digits are not returned in plain ASCII but substituted (e.g. on pages translated to Arabic and Farsi, or all languages like Bengali, Hindi written with Indic scripts).
  • Make sure that your pages do not generate parser errors in expressions by checking at how they look in a dummy Arabic or Farsi translation (note that this does not apply to Hebrew because it does not use by default digits different from those used in Latin Greek and Cyrrillic scripts), look at how it looks in Hindi if for the 1st test you want to avoid testing also the LTR/RTL layout issues.
  • The proposed format "j F Y" will not be consistant across languages, notably for Chinese Japanese and Korean because they only generate unqualified numbers but no easily distinctable month name. Generally these languages require that you write them in reverse order (Y F j) and that you also append a sinogram after each one, and that you never insert any intermediate space! Spaces are also unwanted in Thai, Khmer or Lao even if they translate month names distinctly.