Meta Manual

Posted on by



View the manual for the KEF LS50 META here, for free. This manual comes under the category Speakers and has been rated by 1 people with an average of a 7.5. This manual is available in the following languages: English. Do you have a question about the KEF LS50 META or do you need help? We pioneered the Simulation & Analysis market by introducing automation decades ago. Today, as simulation becomes imperative in product design and development, standing by our founding values, we are a world leader in CAE and we continue to amaze with our innovative solutions.

< Tech‎ | News
Manual
This page documents the publishing process for the weekly Tech News newsletter. It provides guidelines based on our experience in creating this particular newsletter, but might also be used as a guide for other Wikimedia publications that are delivered to multiple wikis.

The following notes are intended to serve as guidelines for the process of publishing the Tech/News weekly newsletter and as a place to gather experiences and best practices learned from the publication and delivery of the newsletter's previous issues. There are more details about about deadlines and inclusion criteria for editors who want to contribute or translate.

Writing guidelines[edit]

Brief version: Tech/News#contribute
Language
You can check your writing in the Hemingway app and the Up-Goer 6 tools that will highlight complex sentences and rare words.
There are a few guides to writing in plain English.
  • SimplyPut.ie gathers useful resources on how to write in plain English and provides a handy list of words and phrases to avoid.
  • US government has a list of words to avoid and the entire site https://plainlanguage.gov/
  • UK government has a similar list, and a writing guide.
  • Kingcounty.gov has a list of words to avoid with alternatives.
For more specific guidelines, you can try the English Wikipedia Signpost's style guide as well as the more general Manual of Style. Consider using prepositions liberally and avoiding grouping long phrasal groups composed of many nouns.
Links
Be careful with links to wikis other than MediaWiki.org, Commons, Wikidata, and Wikispecies. If you want the links to always work in the same way, always use m:Example to link to anything on Meta-Wiki; always use w:en:Example to link to anything on English Wikipedia; always use q:de:Beispiel to link to anything on German Wikiquote.
Code
All visible MediaWiki or HTML tags should be wrapped in <code><nowiki>...</nowiki></code>;
Add the direction of LTR blocks, for RTL languages compatibility. For instance, <code dir=ltr>.mw-ui-constructive</code> will be rendered as a LTR text in a RTL translation.

Meta Manual Of Dgs

Translation
  • Whenever issues contain text similar to one that had already been published, use the same <tvar|name> to reduce amount of work required of translators and take advantage of translation memory.
  • Inline links that are not supposed to be translated should be put inside <tvar> to simplify translations and direct all users to the same page, for example: [[c:somelink|description]];
    • For recurring items, use the same tvar, so that translators can use translation memory more easily. link, link2, link3 etc. are good generic tvar labels.
    • When you put displayed text inside a tvar, add directionality markers so it displays properly on RTL wikis (and ideally also the language): <span>your content</span>
  • &rlm; can solve some RTL problems. Example.
  • Reference links (e.g. to Phabricator tickets) should be at the end of an item, outside the <translate> tags. External links are preferred (even if an interwiki link is possible) because they're automatically numbered.
  • Interface messages (button names, etc.) should be internationalized using {{int:...}}. See mw:Help:Magic words#Localization for details. Append ?uselang=qqx (or &uselang=qqx) to a URL, to show the interface message's variable name. Example.
  • Here are some standardized lines we occasionally have to use:
    • There is no new MediaWiki version this week.
    • MediaWiki <tvar|mwversion>1.36.0-wmf.1</> was scheduled to be deployed on some wikis last week. The deployment was delayed because of unexpected problems.
    • You will be able to read but not edit [[<tvar|somewikis>phab:T1111111</>|some wikis]] for a few minutes on {{#time:<tvar|defaultformat>j xg</>|<tvar|date2>2020-01-01</>|<tvar|format_language_code>{{TRANSLATIONLANGUAGE}}</>}}. This will happen around [<tvar|time>https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200101T05</> 05:00 UTC]. This is for database maintenance.
Icons
  • You can add the 'Recurring item' and 'Advanced item' icons to the start of entries (before the entry's own <translate> marker), by copying these lines:
  • [[File:Octicons-sync.svg|12px|link=|<translate>Recurrent item</translate>]]
  • [[File:Octicons-tools.svg|15px|link=|<translate>Advanced item</translate>]]

Publication schedule[edit]

Meta Manual Free Download

See also: Tech/News/For contributors#When is the work done?
Meta manual

The current distribution date for the newsletter is Monday, at around 3:00 pm (UTC). This deadline is linked to from the upcoming issue.

Meta
TimeWhatHow
Monday to WednesdayAdd draft contentAdd links to noteworthy changes, and if possible start writing their summaries. See Tech/News#contribute.
ThursdayDraft the newsletter
  • Open the Tech/News/Next edition's page.
  • In the #user-notice board in Phabricator
    • Make sure you're looking at All tasks, not just Open ones.
    • Archive items from last week by moving them from the 'In current Tech/News draft' column to the 'Archive' column.
    • Review items in the 'To Triage' column
    • Review items in the 'Announce in next Tech/News' column
    • Review items in the 'Not ready to announce' column to see if they have changed state (are there any that are now closed? Any changed in the last 7 days?)
    • Move items from the 'Announce in next Tech/News' column to the 'In current Tech/News draft' column
    • For all tasks: If it hasn't already been done, then summarize the items. If the task is unclear then ask for suggested wording.
  • Review the threads on wikitech-l and the wikitech ambassadors list to see if there are any topics there that ought to be in Tech News.
  • Check if something will happen concerning Translatewiki.
  • Check for new messages at Talk:Tech/News
  • Check the incident documentation to find anything that would have had a noticeable effect on editors.
  • Add the next upcoming TechCom RfC meeting if the topic has been decided upon.
  • Check the deployment dates, and the 'new version' link, to make sure they are accurate.
  • Write and Format the content. See #Guidelines reminders about writing-style.
  • Prepare the content for translation. You'll need 'Translation admin' rights, or a Translation admin to approve your changes. We use the Translate extension; see how to set up a content page for translation.
  • Request the help of Wikimedia translators through their mailing list at translators-l@lists.wikimedia.org, to translate the early draft of the newsletter
FridayFinalize and freeze the newsletter
  1. Open the Tech/News/Next edition's page.
  2. Make any final edits or changes needed - E.g. check for edits to #user-notice tasks in the last 24 hours.
  3. 'Freeze' the issue by removing the {{tech news draft}} template and any empty sections, and marking the page for translation; after that, subsequent items should be added to the next issue.
  4. Create a draft for next issue by clicking the Next link on the current issue's page.
  5. Update the latest and next redirects so that links from the main page work properly.
  6. Notify translators on their mailing list, and highlight the changes between the early draft and the final version. If no changes were made, send a message anyway to let them know the content is now final.
MondayDistribute the newsletter
  1. Open the edition
  2. Prepare and launch the distribution; see Distribution checklist below.
    • (...)

Distribution[edit]

See an overview of the process in this 2014 blog post

The distribution generally happens on Monday around 3:00 pm (UTC). If you change that time, update the deadline linked to from the upcoming issue.

  1. Do the final polish
    1. Remove the 'deadline' template, and mark for translation.
    2. Open all translations on Meta and check for red links, in case there was an error during the translation.
  2. Generate the multilingual text of the newsletter
    1. Open Tech/News/Sandbox
    2. Replace the existing issue number with the one that's being sent out (for example, week=28);
    3. After the issue number, insert language codes for languages that have at least partial translations, for instance fr|ko|ja|pl|pt|uk. Do not add en for the English version; as the default language, it is automatically included.
    4. Save your edit.
      • If it breaks, check if all languages have been translated properly. (check for missing tvar code elements, unclosed links, etc)
  3. Test the message
    1. Manually test the message on a few wikis (e.g. on your user page) using the whole generated text, and look for issues (red links, line breaks, etc.). You can do this in two different ways:
      • Copy/paste the whole generated text manually on a few of your user pages, and preview without saving;
        • Check that it begins with <section begin=, ends with a timestamp, and that it uses the right edition (both text and link);
      • Use Special:MassMessage for a dry run using a test distribution list (see example); the process is the same as for the actual delivery (described further below), except for the target list.
    2. A good rule of thumb is to check:
      • on the English Wikipedia
      • on another language available
      • on another language not available (defaulting to English)
      • on an RTL wiki
      • on a multilingual wiki (e.g. mediawikiwiki, commons, wikidata, etc)
      • and on a community page in a localized namespace.
    3. Test it exactly like you plan to send it, including the subject of the message. If you see a mistake, test it again after you fixed the mistake.
  4. Launch the delivery
    1. Open Special:MassMessage in another tab or window
      • Page containing list of pages to leave a message on: Global message delivery/Targets/Tech ambassadors
      • Subject of the message (also used as the edit summary): [[m:Special:MyLanguage/Tech/News/2020/50|Tech News: 2020-50]]
      • Body of the message: The whole multilingual text generated earlier, including the fixes for English language dates.
    2. Click on the button on the page; only the English text will show, because it's Meta-Wiki's language
    3. Do a final check, and if everything looks good, click on the button on the page
  5. Wrap up
    1. Thank the translators on their mailing list at translators-l@lists.wikimedia.org.
    2. Send the English version of the newsletter to the Tech ambassadors at wikitech-ambassadors@lists.wikimedia.org in an HTML e-mail (topic: Tech News 2020, week 50). Copy the text of the newsletter from the desktop site. You may have to copy the language bar into a text document and copy it again to get the right amount of formatting.
    3. Publish it on Diff
      • Create a new blog post, copy & paste the content from the wikipage into the body, add a header as Tech/News/2020/50, tag it with #tech-news, categorize it with technical news and technology, set 'Post Status' to 'Draft', click 'Publish' and 'Submit for review'. (see example post)

Structural components of Tech/News[edit]

  • Template:Tech news nav Navigation template between issues (with 1-click creation of the next issue)
  • Tech/News/init, Default content of new issues
  • Global message delivery, used to deliver Tech News to subscribers across wikis

Meta Manual Differential

Retrieved from 'https://meta.wikimedia.org/w/index.php?title=Tech/News/Manual&oldid=20621333'

Meta Manual Dg Shipping

This regex gets meta tags independent of sequence by capturing inside a lookahead.
Further uses the branch reset feature for different quote styles of values.
The pattern can be tested here: https://regex101.com/r/oE4oU9/1
<?PHP
function getMetaTags($str)
{
$pattern = '
~<s*metas
# using lookahead to capture type to $1
(?=[^>]*?
b(?:name|property|http-equiv)s*=s*
(?|'s*([^']*?)s*'|'s*([^']*?)s*'|
([^'>]*?)(?=s*/?s*>|sw+s*=))
)
# capture content to $2
[^>]*?bcontents*=s*
(?|'s*([^']*?)s*'|'s*([^']*?)s*'|
([^'>]*?)(?=s*/?s*>|sw+s*=))
[^>]*>
~ix';
if(preg_match_all($pattern, $str, $out))
return array_combine($out[1], $out[2]);
return array();
}
// usage
$meta_tags = getMetaTags($str);
?>