Thanks a lot ! I've just tested the OCR on French wikisource, and it seems to work, efficiently AND diligently :)
Nov 13 2020
May 7 2020
Sorry, I did not remember that bug was language sensitive... mine is French. generally, in English, the bug does not appear...
Apr 13 2020
@Hsarrazin Hi, when does this message appear? When you're viewing an existing topic, creating a new one, or answering to a post? Can you copy link to post/flow board?
in all cases... sometimes it's when creating a new post, sometimes editing, sometimes answering...
Apr 11 2020
and again "[16ccf92c-443b-4708-86ca-568a3e8e00b9] Caught exception of type Flow\Exception\NoParserException"
message is "Une erreur s’est produite. Le message d’erreur reçu était : internal_api_error_Flow\Exception\NoParserException"
Dec 17 2019
Moreover, the problem does not concern ''only'' enwikisource, but all wikisource that use this tool, frwikisource being impacted very much as well...
Oct 31 2019
Yes, it's exactly that... I looked for a previous report on Phabricator, but could not find it :)
Oct 30 2019
On frwikisource, we repaired dozens of files with missing pages... no purge of pages, books or files on commons works...
I was about to create a report for the same problem...
c'était sur cette version https://www.wikidata.org/w/index.php?title=User:Hsarrazin/test4&oldid=1041747735
Of course, I updated to try and solve the problem... https://www.wikidata.org/w/index.php?title=User:Hsarrazin/test4&oldid=1041721691
thanks for taking my question as a request for feature :)
hmmm... yes... but how could we know on which dashboard should be those with neither statement (yet) ?
Oct 20 2019
Thanks so much !
Oct 15 2019
Thank you so much !
From a totally different pov (wikisource), this would be nice too for links to "work pages" that can be DISAMBIG, but also REDIRECT as long as we have only 1 edition of a text... :)
Sep 18 2018
Aug 25 2018
Ça marche ! merci @Ebe123 \o/
Aug 23 2018
Merci @Ebe123 quand aura lieu le prochain déploiement ?
Aug 21 2018
The problem is to ping the members of a specific project on wikidata, for discussions outside the project, (on property discussion, on the project chat, etc.), because all members of the project are potentially concerned by the discussion.
A mailing list or a newsletter would be no use at all for this purpose.
Jul 25 2018
Apr 9 2018
Jan 22 2018
Some contributors in French are very perturbated by this notation, even thinking that the entry (5. siècle} was wrong, and trying to add Q8095 instead...
Sep 26 2017
the first 2 screenshots show page editing normal and broken (no picture of the page, code only) and index editing (broken first, and normal with menus and input cells).
Aug 13 2017
You must understand that, to French people, the mere possibility to publicly cross-search personal data for people that are not "public" (i.e. famous... in a way or another) is very, very sensitive....
It would also allow to search the database of users for any property.
Totally agree with Ash_Crow here... this is NOT a good idea :((
Jun 6 2017
For tasks that failed, it would be nice to have a sign indicating the state, and proposing to retry when possible, or to cancel and remove the task when the cause is a file missing on IA (I've seen quite a lot of these).
Sep 1 2016
Nov 25 2015
Yep, I confirm the exact same problem. when trying to type words with ^ accent (like forêt) or ¨ (like naïade), the classic typing method does not work in properties and labels of an item, while it works perfectly in the discussion pages.
Oct 17 2015
is this something that would allow NOT to use template tiret and tiret2 (on frws) anymore ?