Pinging @Tagishsimon since it seems that you discovered this issue a few days ago. Is it already reported somewhere else?

Great, thanks a lot!

Hi @CamelCaseNick , could you give us more details about the issue you encounter with the umlaut character?

• example queries where the character switch is happening
• how this affect Listeria (example, error message, etc.)

Thanks a lot for the update @MisterSynergy !

The change is now enabled, if you encounter any issue, feel free to report it here!

Just a reminder that community people regularly come to me asking when we can implement the integration of Lexicographical data on Wiktionaries. Example from today on French Wiktionary.

FYI, it keeps happening, for example today with an announcement on Commons https://commons.wikimedia.org/wiki/Commons:Village_pump#Wikidata_descriptions_changes_to_be_included_more_often_in_Recent_Changes_and_Watchlist

Waiting for the result of discussions here and positive feedback from Amir or another LangCom person.

I think we can go for it :)

The system analyzing dates input tries its best to guess what's the entered format, based on the content, the characters used to split the numbers, etc. However, sometimes it's ambiguous, in that case "03/11/1931" could be MM/DD/YYYY or DD/MM/YYYY. When the character / is used, we assume that the input is "the American format". With dots it would be interpreted differently.
That's not ideal, and it's quite difficult to guess what the user wants to enter without adding any constraints.
Closing the ticket because in that case, this behaviour is done on purpose.

It's been two weeks and we didn't hear any veto from @Amire80 or @jhsoby, so I think we can move forward with it. @Mbch331 will you prepare a patch that we can merge?

Hey @Pyfisch @matej_suchanek Are you performing revision-delete edits, and did you encounter the same issue? Thanks :)

Browsers used by Ymblanter when encountering the issue: Firefox last version (on Linux Manjara) and possibly Palemoon last version (Windows 7). Could we try to reproduce on these specific systems?

Thanks Matej!

@Amire80 @jhsoby Before we move forward, could you have a look and let us know it it looks relevant from your side? Thanks!

@Gehel Could you have a look, and as we had several mentions of it over the past weeks, maybe reconsider the priority of this task? Thanks a lot!

This looks good as a text for the "final" Query Builder. My proposal (cf Mattermost channel) was for the SQB test system on https://query-builder-test.toolforge.org/ : "Welcome to the test system of the Simple Query Builder. Please note that this is a work in progress, not all features are included, and it can sometimes be broken. Feedback is welcome here." Thanks for adding it :)

@jhsoby Ping? :)

Per announcement, unless there is a strong opposition from the community to this change we will implement it on October 20th.
Thanks a lot to everyone giving constructive feedback under this ticket!

Thanks for mentioning this! We will keep it in mind for when the Bridge is deployed on several wikis - for now, as it's only enabled on Catalan Wikipedia, the edits come only from there.

Thanks a lot, and thanks for updating https://www.wikidata.org/wiki/Help:Monolingual_text_languages . I also updated https://www.wikidata.org/wiki/User:Lea_Lacroix_(WMDE)/List_of_lists_of_languages

Hi Abian, thanks for your report :)

@Mohammed_Sadat_WMDE FYI, to check if it doesn't happen with the Weekly Summary

In T258067#6308987, @Addshore wrote:

Would be good to get the API response here somehow! :)

Thanks for the ping, we will have a look more in details and come back to you.

Another case where a user is confused by the error message: https://www.wikidata.org/w/index.php?title=Wikidata:Project_chat&oldid=1191761458#Could_not_save_due_to_an_error._Malformed_input

Can we keep the task open a few more days? I just sent the announcement to the community https://www.wikidata.org/wiki/Wikidata:Project_chat#Special:FewestRevisions_to_be_disabled and I just want to make sure that there's no strong veto. But everything should be fine.

@Charlie_WMDE Are you OK with that change? Could you make some suggestion for the sentence where "incorrect" would appear two times?

Some news got posted here: https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2020-May/002298.html

Hello all,
I have a question about the hackathon showcase :) https://etherpad.wikimedia.org/p/wmhackshowcase2020
Who's going to present? (we can only allow one person)
You indicated that you don't want to be recorded: however, the situation changed a bit, as we will stream the whole thing directly online. Is it fine if you don't share your camera, only your screen, and your voice so you can present?
If not, you could also prepare a video that we would broadcast for you during the showcase.
Thanks for your understanding!

Thanks! You will announce it on Wikidata right?

I'll copy the answer I provided on the "contact the development team" page:

Agreed.

@MarkTraceur Awesome, thanks for the quick answer.
Just to make sure I understand correctly: does that mean that wikis who didn't touch the current code will have their graphs working again after these 3-4 weeks? Or do they have to change something in the code?

Hi @MarkTraceur, is there any fresh update to share about the maintenance of the Graph extension? :)

@Amire80 Indeed, this is due to caching. Usually, purging the page or a null edit fixes the problem.

Do we have a rule regarding merging new tasks into old tasks?

Thanks for the quick fix!

Since these two languages have been added as monolingual language code, we can move forward with Lexemes as well.

No comment has been added, we can move forward with this and enable nrf-gg and nrf-je.

This is still happening on Wikidata, recent example discussed here. @Lydia_Pintscher could we look at it again?

@Ladsgroup Do you know where the Wikidata conversion table is stored and how to add new entries?

@Salgo60 Please remember that Phabricator is a public space, and personal data of other people should probably not be exposed there.
As for Neo4j, we had a look at it but it does not match with our product at the moment, as it's not handling triple endpoint and sparql.

@Ayack The issue should now be fixed: can you try it from your side and let us know if you encounter further issues?

Thanks a lot \o/

So I guess it has not been deployed yesterday?

Yes please :) It's a low percentage but it's still far from zero. Can we also look at the example queries?

Hello all,
Reviving this old ticket, I wanted to ask if there are still objections to move forward with implementing nrf-gg and nrf-je codes for monolingual text. @Amire80, @GerardM, @jhsoby could you have a look and let us know what you think?
This code could be used for example in this case.
The recent request comes from here.