User talk:Johan G/Template:This months newsletter: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(→‎Grammar and spelling: Apostrophe or not?)
 
Line 3: Line 3:


—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:39, 19 November 2017 (EST)
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:39, 19 November 2017 (EST)
== Translation and preload parameters ==
Hi [[User:Johan G|Johan]],<br>
there are a few points that I would like to add to your great Newsletter (preload) template project. They don't have to be done all and now but we should at least discuss them before moving it out of the sandbox.
* We should add language support to <u>all</u> templates connected to Newsletters.
** The {{tl|Newsletter-header}} is currently translated as {{tl|De/Newsletter-header}}. Writing a default {{tl|Newsletter-header}} template would require just a few {{tl|LangSwitch}} and {{obr}}#time:{{cbr}}. Your preload template also has no language support in this state yet. It would make sense translating both when connecting them (if you want to connect them).
** As dates would need to be translated as well (like de/FG Newsletter März 2017) we should use {{obr}}#time: F Y{{!}}now{{!}}lang{{cbr}} function instead of <nowiki>{{CURRENTYEAR}} and {{CURRENTMONTHNAME}}</nowiki>.
** Looking at {{tl|Newsletter-header}} your template needs to be prepared to the displayed phrase used in {{tl|Newsletter-header}}: ''Help us write <u>the next edition</u>'' before connecting them. We could better use optional parameters like "<code>alttext1=Help us{{!}}alttext2=the next</code>" there.
* Use automated [https://www.mediawiki.org/wiki/Manual:Creating_pages_with_preloaded_text#Using_parameters preload prameters] for Month and year ($1, $2 for 12 and 2017 instead of "FIXME"). This would make it easier to create a new Newsletter. And this can fix your Category issue by adding ''':''' to <nowiki>[[</nowiki>''':'''Category:... when subpage-to= is used.
* Small changes to the [[User:Johan G/Template:This months newsletter/Newsletter example|Newsletter example]] like
** add <nowiki>== AI ==</nowiki> (great response to it at [[FlightGear Newsletter July 2017#AI|this edition]])
** add chinese "[[Talk:Next_newsletter|Translators required]]".
If you agree and need need someone to do this (or don't really know what i want to do) I would like to implement these ideas as a suggestion to your great template and a new translated sandbox {{tl|Newsletter-header}}. I have a detailed plan and working code but want your permission first as these are complex contributions to your sandbox work under your development.
<br>[[User:Skybike|Skybike]] ([[User talk:Skybike|talk]]) 10:24, 20 December 2017 (EST) (Translator of the German Newsletter)

Revision as of 15:24, 20 December 2017

Grammar and spelling

Should it not be "This month's newsletter", (in essence with an apostrophe)?

Johan G (Talk | contribs) 12:39, 19 November 2017 (EST)

Translation and preload parameters

Hi Johan,
there are a few points that I would like to add to your great Newsletter (preload) template project. They don't have to be done all and now but we should at least discuss them before moving it out of the sandbox.

  • We should add language support to all templates connected to Newsletters.
    • The {{Newsletter-header}} is currently translated as {{De/Newsletter-header}}. Writing a default {{Newsletter-header}} template would require just a few {{LangSwitch}} and {{#time:}}. Your preload template also has no language support in this state yet. It would make sense translating both when connecting them (if you want to connect them).
    • As dates would need to be translated as well (like de/FG Newsletter März 2017) we should use {{#time: F Y|now|lang}} function instead of {{CURRENTYEAR}} and {{CURRENTMONTHNAME}}.
    • Looking at {{Newsletter-header}} your template needs to be prepared to the displayed phrase used in {{Newsletter-header}}: Help us write the next edition before connecting them. We could better use optional parameters like "alttext1=Help us|alttext2=the next" there.
  • Use automated preload prameters for Month and year ($1, $2 for 12 and 2017 instead of "FIXME"). This would make it easier to create a new Newsletter. And this can fix your Category issue by adding : to [[:Category:... when subpage-to= is used.
  • Small changes to the Newsletter example like

If you agree and need need someone to do this (or don't really know what i want to do) I would like to implement these ideas as a suggestion to your great template and a new translated sandbox {{Newsletter-header}}. I have a detailed plan and working code but want your permission first as these are complex contributions to your sandbox work under your development.
Skybike (talk) 10:24, 20 December 2017 (EST) (Translator of the German Newsletter)