I've absolutely no idea where this title duplication comes from... As a temporally fix, I've added this peace of code to the global CSS to hide the second titles:

.page-Special_RecentChanges h4 + h4 {
    display: none;
}

No idea if this makes sense / is in scope

Yes it is :)

In the LinguaRecorder library, when switching from the listening state to the recording state, we had to disconnect a first ScriptProcessorNode (see doc) and then connect the second one. If some audio sample arrived in-between, they got lost, creating the small audio breakout. To avoid this, I now use only one ScriptProcessorNode (which also simplifies other functions, because we no longer need to manage node disconnection / reconnection in many places).

See this commit.

I've made a first try by implementing somehow the second solution: A buton allowinf the user to record one word, which will be played one second later. Lets see how users will react.

Done in this commit.

the slash in the word seems like the obvious candidate

Yes it is the cause of the warning, the filename mentioned is a proposal from MediaWiki for a legal filename.

Other wikis can now be supported (commit). I've added the Wiktionary, but other could be easily be added in the future.

I finally changed the datatype, it should be better now.

You're right. But as Lingua Libre support way more languages than wikibase do, so it is not possible to set the correct language in all cases. I see three solutions:

• hide with a small JS/CSS snippets the language (as a temporary fix)
• set the correct language if possible, and for unsupported languages use mul (multilingual) (need a bit of development, but it's not very clean in my opinion);
• change the datatype of this property from monolingual text to simple string, as the language is already explicitly defined in an other property (this is the one I prefer, but need to edit manually the DB).

@LucasWerkmeister just pointed out on twitter that items sometimes jump from one line to the next/previous, due to the width difference of the to be read state (it has currently a small border that the other states doesn't have).

Thanks for your feedback!

A first try has been made in this commit, but only one source is yet supported (Wikipedia currently).

A qualifier can now be appended to homograph words to precise their meaning, in the following format: "transcription (qualifier)"
If someone think this is not enough to manage every use-cases, just reopen this task.

Current messages are:

@Aklapper Thanks a lot for your comments and tour help! :)

• if you want to have one project in Wikimedia Phabricator (and e.g. use workboard columns for categorizing subprojects), or want subprojects

Using workboard columns will be easier for us I think (the sub-projects aren't big enough in my opinion).

Huuuu (bis), I've completely forgotten this page... Lingua Libre is not ready (yet!) to welcome developers with little experience of MediaWiki, so I removed it from the page.

Huuu, this is the repository of an old version of Lingua Libre, deprecated since one year. With the project grant linked in the description, when we moved to the current version, which is a complete rewrite of the old one and not directly related to WMFr anymore : https://github.com/lingua-libre.

That's it. Wikimedians are more used nowadays to report bugs / ask features on phabricator (and they don't need to create a new account), and the board feature here better fits our needs.
Furthermore, in a later point in time when the code base will be more stable, I would like to move the git repository from github to gerrit, to have all inside the Wikimedia ecosystem. Even it's easy to move a repository, moving issues is quite a harder job...

Since everybody seems to agree that the wikitext editor should be the default editor, I've changed the configuration in this way, "not as a perfect solution, but as a way of somewhat improving the situation as soon as possible" as @Whatamidoing-WMF said.

Yes sure:

@Tgr I would be interested in using this extension on a Mediawiki 1.30, do you plan to finish this task?

@RolandUnger Oh, yes, didn't find it before creating this ticket, I close it.

In T180361#3769662, @Thibaut120094 wrote:

In T180361#3768722, @Nirmos wrote:

Here's JavaScript that does the trick:

$( function() {
	'use strict';
	$( '.reference' ).each( function( i, e ) {
		var next = $( e )[ 0 ].nextSibling;
		if ( next ) {
			if ( next.nodeType === 1 ) {
				if ( $( next ).hasClass( 'reference' ) ) {
					$( e ).after( '<sup class="cite_virgule">,</sup>' );
				}
			}
		}
	} );
} );

However, for this to work correctly, you would have to remove the reference class from Modèle:,. Otherwise, it would add commas after the commas that have been added manually.

Also, the styles in https://fr.wikipedia.org/wiki/MediaWiki:Common.css that target .reference and .exposant would have to be changed to include .cite_virgule so that the commas are on the same height as the references. Once this is done, it will work.

If it's in JavaScript, the commas won't show up for people who disabled Javascript on their browser and in the printed or PDF version of the article.

There is a massive misunderstanding arround thoose coordinates, there are many people which does not understand what they represent. Imho, the best solution would be to simply remove them, and enable instead the right-click popup everywhere (cf T178338).

This feature is in the ext.kartographer.preview module, which is load only during page preview. I'm also in favour of activating this feature all the time.

@Gehel In fact, the result you got isn't an issue imho, it's the solution @IGW (the author of the issue) and I suggested earlyer in this ticket.

Same problem on frwiki, got this error in my JS console in my firefox 53.0.3 when trying to display a maplink on fr:Paris:

We have the same issue reported currently on frwiki from contributors who don't understand why the links to OSM/GMaps/... place a marker shifted from several kilometers.

Done in https://fr.wikipedia.org/w/index.php?diff=137531683

@Esanders Yes, but this other editor works only inside the visual-editor, is very small, and stores all the GeoJSON code directly inside the page (which is quite awful when creating maps with a lot of elements on it). KartoEditor works on maps stored in the namespace Data from Commons (importable from every wiki), and has a lot more customization options (color, size, icons, opacity, popup, ...) 🐱.