Jump to content

User talk:SPage (WMF)

Add topic
From mediawiki.org
Latest comment: 7 years ago by 160.167.179.59 in topic Tech News: 2016-20

Hi, my Talk has been Flowified (yours can too, visit Special:Preferences > Beta features and check "Flow on user talk"). If you "Start a new topic here", you'll automatically be watching it (starred) and Echo will notify you if I respond.

It's probably faster to contact me on IRC #wikimedia-tech connect, I'm spagewmf

Sadly, I am on a medical leave of absence from work. If you need to reach me, send a Google Hangouts message

Previous discussion was archived at User talk:SPage (WMF)/Archive 1 on 1 October 2015.

Dictionary

[edit]

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Farsi Hossein maryam (talk) 00:47, 5 October 2015 (UTC)Reply

I don't understand your topic. There is a Persian (Farsi) dictionary, https://fa.wiktionary.org/ SPage (WMF) (talk) 19:42, 6 October 2015 (UTC)Reply
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Front-end vs Front end

[edit]

Just saw your redirect over at the standards group. English is pretty lax when it comes to rules, I was astonished myself, but oriented on English Wikipedia: https://en.wikipedia.org/wiki/Front_end_development

You should get active there too! ;) Volker E. (WMF) (talk) 09:47, 13 October 2015 (UTC)Reply

English isn't lax, writers are. The hyphen is right. Three-letter acronym, third-party software, front-end development, client-side programming. Otherwise it can read like front end development (!?) and that momentary hesitation where your brain picks the right interpretation impedes reading. Punctuation for readability FTW. Meanwhile I continue to look for good party software :-) SPage (WMF) (talk) 19:39, 13 October 2015 (UTC)Reply

Tech News: 2015-45

[edit]

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


<labeledsectiontransclusion/begin /> <labeledsectiontransclusion/end /> 16:43, 2 November 2015 (UTC)

MediaWiki message delivery (talk) 16:43, 2 November 2015 (UTC)Reply

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Tech News: 2015-46

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 17:18, 9 November 2015 (UTC)

MediaWiki message delivery (talk) 17:18, 9 November 2015 (UTC)Reply

Tech News: 2015-47

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 19:39, 16 November 2015 (UTC)

MediaWiki message delivery (talk) 19:39, 16 November 2015 (UTC)Reply

Use of <tt>

[edit]
Need to ask wikitech-l, probably kbd is better.

Just FYI, the use of <tt> is obsolete, that why it was changed to <code>.

Also, making such changes in translation units where that's the only change, unless I'm wrong and the Translate extension is able to merge it transparently, is disruptive for other languages, forcing translators to check what's changed and update those units (otherwise, the text is reverted to English unless the translation is checked). Would you make those changes on the translated pages if the translation is approved? Ciencia Al Poder (talk) 12:00, 21 November 2015 (UTC)Reply

Hi there. tt has exactly the right semantics and appearance for a filename, see http://www.w3.org/TR/html4/index/elements.html : fixed-width text without the shading of <code>. If everything uses <code> then paragraphs become much harder to read with too many bordered text spans. A filename is not computer code nor is it instruction to a computer, but it's not regular English either. I believe I'm making wiki pages easier to read by replacing <code> with <tt>.
But you're right, it's obsolete and generates errors in HTML5 validators. Is that a showstopper? I'd like to take it to the experts at mail:wikitech-l.
If it is, then I think <span style="font-family:monospace"> gives the same effect in some browsers, though it's a complete pain to type. Maybe we could have a <span class="tt">. However, when I try it, weird stuff happens in Firefox :-(
  • You then edit LocalSettings.php (tt)
  • You then edit LocalSettings.php (styled span)
  • You then edit LocalSettings.php (kbd)
  • You then edit LocalSettings.php (code)
I don't want to needlessly mess up translations. I frankly don't understand the inner details of how they work. If all that's changed is markup, it seems translators would just make the same change. When you say
> "Would you make those changes on the translated pages if the translation is approved?"
I'm not sure what you mean by "if the translation is approved", approved by whom? Are you asking me to make markup changes to all translations that get reverted to English because of my efforts to improve legibility? I guess so.
For templates invoked with {{TNT}} I've learned the only way to see a fix is to click the link in "since it was last _marked for translation_." Otherwise I don't mark for translation. When someone does click _marked for translation_, Special:PageTranslation has a checkbox "Do not invalidate translations", it seems that person could check it seeing as this is just a minor, but worthwhile, presentational thing.
Thanks for bringing this up, it's worth getting right. SPage (WMF) (talk) 02:49, 23 November 2015 (UTC)Reply
Thanks for the reply.
I don't think using <tt>, although being obsolete, would cause problems (at least for now), but it's worth using alternatives instead of continue using it, or even using it on new places.
You're right, LocalSettings.php is a file name and there's no semantic way to represent it. Still, we can use kbd instead, since arguably, it's a filename and is something that can be typed on a console terminal...
I don't have access to translation stuff, except editing translations, so I don't really know how this works, but usually I found Translate extension not to apply such changes cleanly and they need to be manually applied on all translations. That's why you should be aware of this, and avoid such trivial changes on translated pages. Fortunately, this page is only translated on few languages, so those translation units are generally not translated anyway. Ciencia Al Poder (talk) 10:53, 23 November 2015 (UTC)Reply

Tech News: 2015-48

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 20:26, 23 November 2015 (UTC)

MediaWiki message delivery (talk) 20:26, 23 November 2015 (UTC)Reply

Tech News: 2015-49

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 16:16, 30 November 2015 (UTC)

MediaWiki message delivery (talk) 16:16, 30 November 2015 (UTC)Reply

Tech News: 2015-50

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 17:52, 7 December 2015 (UTC)

MediaWiki message delivery (talk) 17:52, 7 December 2015 (UTC)Reply

Tech News: 2015-51

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 17:42, 14 December 2015 (UTC)

MediaWiki message delivery (talk) 17:42, 14 December 2015 (UTC)Reply

Tech News: 2015-52

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 18:29, 21 December 2015 (UTC)

MediaWiki message delivery (talk) 18:29, 21 December 2015 (UTC)Reply

Tech News: 2016-02

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 16:59, 11 January 2016 (UTC)

MediaWiki message delivery (talk) 16:59, 11 January 2016 (UTC)Reply

Tech News: 2016-03

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 17:56, 18 January 2016 (UTC)

MediaWiki message delivery (talk) 17:56, 18 January 2016 (UTC)Reply

Tech News: 2016-04

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 16:38, 25 January 2016 (UTC)

MediaWiki message delivery (talk) 16:38, 25 January 2016 (UTC)Reply

Tech News: 2016-05

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 21:02, 1 February 2016 (UTC)

MediaWiki message delivery (talk) 21:02, 1 February 2016 (UTC)Reply

Tech News: 2016-06

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 18:58, 8 February 2016 (UTC)

MediaWiki message delivery (talk) 18:58, 8 February 2016 (UTC)Reply

Tech News: 2016-07

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 16:16, 15 February 2016 (UTC)

MediaWiki message delivery (talk) 16:16, 15 February 2016 (UTC)Reply

Tech News: 2016-08

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 18:22, 22 February 2016 (UTC)

MediaWiki message delivery (talk) 18:22, 22 February 2016 (UTC)Reply

Tech News: 2016-09

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 20:12, 29 February 2016 (UTC)

MediaWiki message delivery (talk) 20:12, 29 February 2016 (UTC)Reply

Tech News: 2016-10

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 20:24, 7 March 2016 (UTC)

MediaWiki message delivery (talk) 20:24, 7 March 2016 (UTC)Reply

Tech News: 2016-11

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 18:37, 14 March 2016 (UTC)

MediaWiki message delivery (talk) 18:37, 14 March 2016 (UTC)Reply

Tech News: 2016-12

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 16:04, 21 March 2016 (UTC)

MediaWiki message delivery (talk) 16:04, 21 March 2016 (UTC)Reply

Tech News: 2016-13

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 19:43, 28 March 2016 (UTC)

MediaWiki message delivery (talk) 19:43, 28 March 2016 (UTC)Reply

Tech News: 2016-14

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 22:13, 4 April 2016 (UTC)

MediaWiki message delivery (talk) 22:13, 4 April 2016 (UTC)Reply

Tech News: 2016-15

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 20:44, 11 April 2016 (UTC)

MediaWiki message delivery (talk) 20:44, 11 April 2016 (UTC)Reply

Tech News: 2016-16

[edit]

<labeledsectiontransclusion/begin />

<labeledsectiontransclusion/end /> 20:40, 18 April 2016 (UTC)

MediaWiki message delivery (talk) 20:40, 18 April 2016 (UTC)Reply

Tech News: 2016-17

[edit]

<labeledsectiontransclusion/begin />

21:02, 25 April 2016 (UTC)

MediaWiki message delivery (talk) 21:02, 25 April 2016 (UTC)Reply

Tech News: 2016-18

[edit]

<labeledsectiontransclusion/begin />

20:09, 2 May 2016 (UTC)

MediaWiki message delivery (talk) 20:09, 2 May 2016 (UTC)Reply

Tech News: 2016-19

[edit]

<labeledsectiontransclusion/begin />

23:22, 9 May 2016 (UTC)

MediaWiki message delivery (talk) 23:22, 9 May 2016 (UTC)Reply

Tech News: 2016-20

[edit]

<labeledsectiontransclusion/begin />

16:01, 16 May 2016 (UTC)

MediaWiki message delivery (talk) 16:01, 16 May 2016 (UTC)Reply

tanks yuo 160.167.179.59 (talk) 22:29, 30 January 2018 (UTC)Reply

A barnstar for you!

[edit]
The Writer's Barnstar
These are great writing tips. Documentation/Style_guide Xephyr826 (talk) 23:03, 26 January 2017 (UTC)Reply