Community Wishlist Survey 2021/Untranslated

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

These proposals need translation. Once translated, the Wishlist team will move them to the appropriate category.

Antworten auf Diskussionen via mobiler Webseite

Edit proposal/discussion

  • Problem: Wenn man auf einer Diskussionsseite in mobiler Ansicht antwortet und sich nicht im Wikitext-Modus befindet, dann werden Antworten nicht eingerückt, sprich der zusätzliche Doppelpunkt wird nicht gesetzt. Dieser Bug dürfte sich vermutlich schnell lösen lassen.
  • Who would benefit:
  • Proposed solution:
  • More comments:
  • Phabricator tickets:
  • Proposer: --Smarti (talk) 18:06, 16 November 2020 (UTC)

Discussion[edit]

  • This doesn't seem like an issue for CommTech for multiple reasons, 1) it is not a feature request or significantly old bug and 2) the discussion tools team is working on topics like this one already. --Izno (talk) 22:06, 16 November 2020 (UTC)
    Is it a guess or do know it for sure, they are working on it? --Smarti (talk) 23:51, 16 November 2020 (UTC)
    I think I randomly found the correct ticket.
    --Smarti (talk) 00:51, 17 November 2020 (UTC)
    Mediawiki: Using correct indenting/bulleting --Smarti (talk) 01:01, 17 November 2020 (UTC)

উইকিঅভিধান

Edit proposal/discussion

  • সমস্যা:
  • কে উপকৃত হবে:
  • প্রস্তাবিত সমাধান:
  • আরো মন্তব্য:
  • ফ্যাব্রিকেটরে টিকেট:
  • প্রস্তাবকারী: Sumasa (talk) 06:15, 17 November 2020 (UTC)

আলোচনা[edit]

উইকিনমস্কার,

সময় সুযোগ থাকলে উইকিঅভিধানে কাজ করে থাকি। জ্ঞান হওয়া ইস্তক আমাদের নজরে যেসব শব্দ, বাক্-ধারা, প্রবাদ ইত্যাদি আসে, উইকিঅভিধানে তার কিছু কিছু সংযোজন করে যাই। তবে কখনো কখনো বলা হয় - 'এটা উইকিতে নেই,...'! হ্যাঁ, নেই বলেই তো নতুন সংযোজন করে উইকিকে সমৃদ্ধ করা দরকার। আমার ধারণা, উইকির উন্নয়নকামী স্বেচ্ছাসেবী মানুষদের মধ্যে অনেক বাংলা ভাষার গবেষকও আছেন, যাঁরা আমাদের মতো সংযোজনকারীদের যাবতীয় নতুন বাংলা শব্দ, বাক্-ধারা, প্রবাদ ইত্যাদি গবেষণা ও সম্পাদনা করে সংরক্ষণ করবেন।

নতুন প্রস্তাব: বাংলা বাক-ধারা এবং প্রবাদের পাশাপাশি অন্তত একটা করে উদাহরণ দেওয়া দরকার, [যেমন: রাঘব বোয়াল - তদন্ত হলে অনেক রাঘব বোয়াল ধরা পড়বে।] যাতে পাঠক/দর্শকদের কছে বিষয়টা পরিষ্কার হয়ে যায়। এক্ষেত্রে উইকি পাতার নকশা-ও সেইভাবে করা দরকার। প্রয়োজনে উদাহরণ লিখে দিতে পারি।

ধনবাদসহ,

Sumasa (talk) 06:15, 17 November 2020 (UTC)

  1. REDIRECT Community Wishlist Survey 2021/Miscellaneous/ Fix the Content Translation bug (Consertar o bug do tradutor de conteúdo)

Insertion rapide de wikicodes personnalisés

Edit proposal/discussion

  • Problem: Liste de codes à insérer trop limitée
  • Who would benefit: Rapidité de travail
  • Proposed solution: Actuellement, il existe 36 wiki-codes prédéterminés (insertable wiki markup) en bas de la page de modification des articles, et il suffit de cliquer sur un des codes pour l'insérer dans l'article (exemples sur le wiki en français : [[Catégorie:]] [[Fichier:]] [[Media:]] [[Spécial:Diff/]] [[Spécial:Contribs/]] #REDIRECTION [[]] · [[commons:|]] [[m:|]] [[n:|]] [[q:|]] [[s:|]] [[b:|]] [[wikt:|]] [[v:|]] [[d:|]] · <></> <code></code> <math></math> <small></small> <u></u> <ref></ref> <ref name=""></ref> {{Références}} <noinclude>, etc.

Il serait extrêmement pratique de pouvoir créer moi-même mes wiki-codes prédéterminés (insertable wiki markup) et de les rendre disponibles en plus de la liste déjà existante, afin de pouvoir les insérer par un simple clic. Ce serait ultra rapide ! Par exemple, j'aimerais pouvoir insérer avec un clic le code suivant qui est très long à écrire :

<ref>{{Ouvrage|auteur=|titre=|année=|éditeur=|tome=|page=|pages totales=|lire en ligne=|consulté le=}}</ref>

  • More comments:
  • Phabricator tickets:
  • Proposer: Tubamirum (talk) 18:09, 17 November 2020 (UTC)

Discussion[edit]

В Википедии добавить кнопочку для гуглоперевода статьи.

Edit proposal/discussion

  • Проблема: не все статьи есть на родном языке, много времени уходит чтобы перевести
  • Кто выиграет: читатели
  • Предлагаемое решение: встроить автоперевод - добавить кнопочку для гуглоперевода статьи
  • Дополнительные комментарии:
  • Ссылка на задачу в Фабрикаторе:
  • Предложил(а): denis_73 (talk) 20:37, 17 November 2020 (UTC)

Обсуждение[edit]

В каждом броузере уже есть такая функция. Воспользуйтесь ей. SSneg (talk) 21:39, 20 November 2020 (UTC)
denis_73, Спасибо, что отправили это желание! Мы храним это желание, потому что оно выходит за рамки. Однако мы рекомендуем вам взглянуть на это. Вам может быть интересно: https://www.mediawiki.org/wiki/Content_translation IFried (WMF) (talk) 21:12, 3 December 2020 (UTC)

Insertion rapide de wikicodes personnalisés (Customizable insertable wiki markup)

Edit proposal/discussion

  • Problem: Liste de codes à insérer (insertable wiki markup) trop limitée actuellement
  • Who would benefit: Everyone
  • Proposed solution: Rapidité de travail
  • More comments: Actuellement, il existe 36 wiki-codes prédéterminés (insertable wiki markup) en bas de la page de modification des articles, et il suffit de cliquer sur un des codes pour l'insérer dans l'article (exemples sur le wiki en français : [[Catégorie:]] [[Fichier:]] [[Media:]] [[Spécial:Diff/]] [[Spécial:Contribs/]] #REDIRECTION [[]] · [[commons:|]] [[m:|]] [[n:|]] [[q:|]] [[s:|]] [[b:|]] [[wikt:|]] [[v:|]] [[d:|]] · <></> <code></code> <math></math> <small></small> <u></u> <ref></ref> <ref name=""></ref> {{Références}} <noinclude>, etc.

Il serait extrêmement pratique de pouvoir créer moi-même mes wiki-codes prédéterminés (insertable wiki markup) et de les rendre disponibles en plus de la liste déjà existante, afin de pouvoir les insérer par un simple clic. Ce serait ultra rapide ! Par exemple, j'aimerais pouvoir insérer avec un clic le code suivant, que j'aurais personnalisé moi-même, qui est très long à écrire en mode manuel :

<ref>{{Ouvrage|auteur=|titre=|année=|éditeur=|tome=|page=|pages totales=|lire en ligne=|consulté le=}}</ref>

  • Phabricator tickets:
  • Proposer: Tubamirum (talk) 20:36, 17 November 2020 (UTC) (French Wiki)

Discussion[edit]

Sorry, my bad. I support this if you mean something like "own charinsert" Patsagorn Y. (Talk) 01:39, 19 November 2020 (UTC)

Requests or Suggestions

Edit proposal/discussion

  • Proposed solution: La place de position du bandeau d'informations internes serait plus adaptée ailleurs sur la page, en bas ou sous une autre forme, pour libérer le haut qu'il serait préférable de réserver au titre.
  • Proposer: Jeanlouis11170 (talk) 20:47, 17 November 2020 (UTC)

Discussion[edit]

  • @Jeanlouis11170: Parlez-vous de la bannière CentralNotice? Il est intentionnellement au sommet pour s'assurer que les gens le voient. MusikAnimal (WMF) (talk) 16:40, 28 November 2020 (UTC)
  • @Jeanlouis11170: Merci d'avoir soumis ce souhait! Nous archivons ce souhait car nous ne contrôlons pas le placement de telles bannières. C'est une question et une décision communautaires - pas une question technique. Mais merci encore pour votre soumission! IFried (WMF) (talk) 20:40, 3 December 2020 (UTC)

ログアウトの確認ダイアログ

Edit proposal/discussion

  • 問題点: Wikipediaのページ右上に表示される「ログアウト」メニューをクリックすると、即座にログアウトが実行されてしまいます。ログアウトするつもりがないのに操作ミスで「ログアウト」をクリックしてしまった場合のために、本当にログアウトを実行しても良いかを確認するダイアログが表示されるような機能を実装して欲しいです。
  • 誰の役に立つか: 操作ミスで「ログアウト」をクリックしてしまう可能性のある全ての利用者
  • 提案された決議:
  • その他のコメント:
  • Phabricator チケット:
  • 提案者: Keruby (talk) 04:04, 18 November 2020 (UTC)

議論[edit]

  • I've discussed a 2-step process for logout somewhere on Phabricator. Not sure where off the cuff. And I feel like this may be a previous proposal? --Izno (talk) 05:14, 18 November 2020 (UTC)

XToolsのログイン状態を維持

Edit proposal/discussion

  • 問題点: XTools (https://xtools.wmflabs.org/) にログインしても、短時間で自動的にログアウトが実行されてしまうため不便です。なので、自動的にログアウトが実行されないように、ログイン状態を維持するオプションをログイン画面に追加して欲しいです。
  • 誰の役に立つか: XToolsでログイン状態を維持したい利用者
  • 提案された決議:
  • その他のコメント:
  • Phabricator チケット:
  • 提案者: Keruby (talk) 04:17, 18 November 2020 (UTC)

議論[edit]

Richiedi feedback

Edit proposal/discussion

italiano: Richiedi feedback

  • Problem: Sometimes it happens to want to add info but do not have sufficient certainty.
italiano: Talvolta capita di voler aggiungere info ma di non avere certezze suffisanti.
  • Who would benefit:
  • Proposed solution: A function could be added to request feedback on a change
italiano: Si potrebbe aggiungere una funzione per richiedere feedback su una modifica
  • More comments:
  • Phabricator tickets:
  • Proposer: Fedesolla (talk) 20:45, 18 November 2020 (UTC)

Discussion[edit]

Шаблоны

Edit proposal/discussion

  • Problem: Шаблоны занимают много места, и их сложно редактировать. Templates take up a lot of memory and space and are hard to edit.
  • Who would benefit: Те, кто работает с шаблонами. Those who work with templates.
  • Proposed solution: Сделать диалоговое окно с редактируемым предпросмотром шаблона. Make a dialog box with an editable preview of the template.
  • More comments: Я сам столкнулся с подобной проблемой, когда редактировал статью "Криптография". I myself faced a similar problem when I edited the article "Cryptography"
  • Phabricator tickets:
  • Proposer: SiriUsBLacK143924 (talk) 14:22, 18 November 2020 (UTC)

Discussion[edit]

Enlaces rojos

Edit proposal/discussion

  • Problema:
  • A quiénes beneficiaría:
  • Solución propuesta:
  • Más comentarios:
  • Informes de Phabricator:
  • Proponente: Dr.Mas20 (talk) 15:08, 19 November 2020 (UTC)

Discusión[edit]

Mi idea es rapida y sencilla aunque no se podria llevar a la practica es crear bots para identificar enlaces rojos utiles de aquellos que no lo son y eliminar los que no lo son y poner enlaces rojos para paginas que si se podrían crear nuevas paginas utiles para la comunidad y los lectores anonimos,esto benefeciaria a ciertos articulos en todos los idiomas llenos de estos enlaces faltos de utilidad y pondria estos enlaces posibilitando la creacion de nuevos articulos utiles para tod@s esa es mi idea para mejorar wikipedia protente Dr.Mas20

উইকিনিউজ পুরোপুরিভাবে চালু করা

Edit proposal/discussion

  • সমস্যা: উইকিনিউজ পুরোপুরিভাবে চালু করা
  • কে উপকৃত হবে:সঠিক খবরের পাঠক
  • প্রস্তাবিত সমাধান:যাচাই-বাছাই করে দ্রুত উইকিনিউজ চালু করা
  • আরো মন্তব্য: এতে ফেইক ও ভূয়া নিউজ ছড়িয়ে পড়া রোহ হবে
  • ফ্যাব্রিকেটরে টিকেট:
  • প্রস্তাবকারী:TAUSIFnAKBAR TAUSIFnAKBAR (talk) 16:54, 19 November 2020 (UTC)

আলোচনা[edit]

আপনাকে আগে বাংলা উইকিসংবাদে অবদান রাখতে হবে। একটা সক্রিয় সম্প্রদায় গড়ে তুলতে হবে। তারপর ভাষা কমিটি উইকিসংবাদ চালুর অনুমতি দিবে। এখানে অবদান রাখুনআফতাবুজ্জামান (talk) 05:10, 23 November 2020 (UTC)

Jahreszeitliche Fotos

Edit proposal/discussion

  • Problem: Illustrationen / Fotos in den Artikeln sollten der aktuellen Jahreszeit entsprechend sein:
  • Wem würde dieser Wunsch helfen: den Nutzern der Enzyklopädie:
  • Lösungsvorschlag: ein Feld für eine Illustration / ein Foto sollte mit mehreren Abbildungen hinterlegt werden können, so dass automatisch nach Jahreszeit die entsprechende = passende Abbildung gezeigt wird: im Winter der Vogelsberg im Schnee bzw. im Sommer in Grün:
  • Weitere Kommentare:
  • Phabricator-Tickets:
  • Antragsteller: --Neptuul (talk) 16:55, 21 November 2020 (UTC): Neptuul (talk) 16:55, 21 November 2020 (UTC)

Diskussion[edit]

navboxの改善をぜひお願いします。

Edit proposal/discussion

  • 問題点: ぺディアにおいて現在のnavboxは、「モバイルモード」からの閲覧が全く出来ず、ぺディア記事内で画像を多用して補足する必要がある記事では(例えば特殊な車両や、鉄道系)記事内のギャラリーに画像を投入した場合、「たびたび画像が多すぎる」または「いやむしろ少ないくらいだ」などと、見解の相違によるトラブルや編集合戦も起こります。この妥協点として、navboxは非常に有効な手段ですが、残念ながら現在の仕様では、「モバイルモード」では全く見ることが出来ず、むしろ中途半端なnavboxは要らない論に発展しています。ぜひ、「モバイルモード」でも見られるように改善を。是非お願い致します。
  • 誰の役に立つか: 不特定多数の多くの閲覧者と、意見対立によるトラブル防止。
  • 提案された決議:
  • その他のコメント:
  • Phabricator チケット:
  • 提案者: 佐渡桶 (talk) 17:42, 22 November 2020 (UTC)

議論[edit]

Spellchecker

Edit proposal/discussion

  • Problem: One of the most important aspects copy-editing workflow for users is finding and fixing spelling mistakes and typos.
  • Who would benefit: Editors who would have less frustration in their work and readers who would read a higher quality articles.
  • Proposed solution: There is something in Persian Wikipedia which I would expect can be used as inspiration and turn into an extension. That tool is called Check Dictation. When an editor who enabled the gadget sees an articles, on top of the page, they see list of mistakes and inside the article they get color coded. It actually has different colors for different issues: Typos, bad wikitext, informal words, links to disambig pages, and many more types. Here's an example File:Rechtschreibung-fawiki.png. You can also define per-article list of okay words an example. The code for the gadget can be found in here but it's highly hard-coded to fawiki and it can be improved drastically.
  • More comments:
  • Phabricator tickets:
  • Proposer: Amir (talk) 18:31, 16 November 2020 (UTC)

Discussion[edit]

I think most operation systems and browsers support spellchecking on their site so this is not needed in MediaWiki. --GPSLeo (talk) 18:40, 16 November 2020 (UTC)

@GPSLeo You wouldn't see the typos unless you go to edit mode. How to find them in articles is not doable with browsers and operating systems. Amir (talk) 19:33, 16 November 2020 (UTC)
Ah, you want a tool to find mistakes in articles just while reading not for editing. I did not got this. Now I understand and think this could be useful. --GPSLeo (talk) 21:23, 16 November 2020 (UTC)
The Chrome spellcheck does not work for me when editing. Keepcalmandchill (talk) 03:45, 17 November 2020 (UTC)

There is a similar user script for the MOS called en:User:Ebrahames/Advisor.js on EN.WP. I don't think I've seen a spelling gadget. I also tend to disagree that a spelling gadget is necessary. (Mis)Spellings can be context dependent. --Izno (talk) 21:55, 16 November 2020 (UTC)

@Izno The spelling gadget would just highlight potential spelling mistakes. Even in the tool in fawiki, you can set highlights as false positive on per-article basis. Amir (talk) 03:33, 22 November 2020 (UTC)

I usually just use Grammarly to check grammar (not sponsored). Félix An (talk) 02:27, 17 November 2020 (UTC)

Would this also take regional variants of English into comparison? English Wikipedia articles can vary depending on regional relevance or by a "first-come first-serve" edit. Tenryuu (talk) 02:29, 17 November 2020 (UTC)

English is not the only language with spelling variances, so good question. --Izno (talk) 18:08, 17 November 2020 (UTC)

Note, that also in Wikisource are various variants of language, language of 100 years old work is different from todaylanguage, but it is also correct. THere should be some project-specific spellchecker, which allows local variants. JAn Dudík (talk) 14:09, 18 November 2020 (UTC)

I think the points made by other users about language variation are good, but as long as the changes are not automated and a human is always involved that person should be able to recognize when a word was incorrectly marked as a misspelling and not act to fix it. For languages that have detailed Wiktionaries, they might be a good source to use for checking what is and isn't a recognized spelling. This orange links gadget has functionalities that also might relevant to this proposal. —The Editor's Apprentice (talk) 19:21, 20 November 2020 (UTC)

@Ladsgroup: thanks for posting this. How does the Check Dictation tool work? Does it use some open-source Persian spellchecker? Or is it handmade with a list of common mispellings? I ask because the Growth team is building "structured tasks", which use machine learning to help newcomers find specific edits to make, e.g. adding wikilinks. Here are notes from a conversation about how to make spellchecking possible across languages, and we're thinking about whether it would have to be done language by language. -- MMiller (WMF) (talk) 17:19, 23 November 2020 (UTC)

@MMiller (WMF) The code for it is w:fa:مدیاویکی:Gadget-CheckDictation.js and it seems it calls a service in the cloud VPS (I didn't write this gadget so I'm not 100% sure of its internals) but I assume it uses a unix library for spellchecking. As I said, it has an exception list for each page as well [1]
The fun thing is that this was originally was developed to find spelling mistakes but it grew to basically any sort of copy-editing issues from links to disambig pages, to unclosed links/templates, to much more. Amir (talk) 00:28, 24 November 2020 (UTC)

I would support the idea, but in the context of a typographic checker, not just a spellchecker. It would check grammar, adjectives, orthography, etc. MarioSuperstar77 (talk) 21:06, 24 November 2020 (UTC)

  • I'm merging a similar wish:
    • Problem: عربى: وجود مدقق لغوي داخلي للنصوص شبيه بما يقوم به برنامج word
    • Proposer: عمر الشامي (talk) 21:09, 22 November 2020 (UTC)

SGrabarczuk (WMF) (talk) 20:25, 3 December 2020 (UTC)

Nachschlagung während des Editierens

Edit proposal/discussion

  • Problem: Looking for a Lemma during Editing
  • Wem würde dieser Wunsch helfen: Allen
  • Lösungsvorschlag: (unbekannt)
  • Weitere Kommentare: keine
  • Phabricator-Tickets:
  • Antragsteller: --Wilhelmus Legrant (talk) 09:21, 23 November 2020 (UTC)

Diskussion[edit]

Oft genug kommt es vor, dass man während des Editierens (innerhalb von Wp!) etwas nachschauen will. Bis jetzt muss man immer:

  • abspeichern und rausgehen,
  • das gesuchte weitere Lemma nachschaun, auch sehen, ob überhaupt vorhanden,
  • zum vorigen Editieren zurückkehren und das gefundene mit einsetzen (falls vorhanden), oder sich hier ggf. mit einem künftigen Rot-Link begnügen.

Ich würde mir sehr wünschen, dass derartiges einfacher und schneller möglich wäre, also ohne das laufende Editieren zu verlassen. Prinzipiell ging das auch heute schon - aber nur, wenn man 2 Computer und 2 Internetanschlüsse besitzt. Wer hat das schon? --Wilhelmus Legrant (talk) 09:21, 23 November 2020 (UTC)

  • Hallo Wilhelmus Legrant Können Sie erklären, warum das Öffnen eines neuen Tabs in Ihrem Browser nicht funktioniert? (Dies ist maschinell übersetzt.) --AEzell (WMF) (talk) 21:23, 3 December 2020 (UTC)

Trouver un affichage plus satisfaisant des formules LaTeX

Edit proposal/discussion

  • Problème: Le système actuel d'affichage et d'export des formules mathématiques laisse grandement à désirer. Les formules sont converties en images où le texte apparaît en noir sur fond transparent, puis insérées dans le fil du texte. Pour cette raison, les formules mathématiques jurent plus ou moins avec le texte environnant :
— sur le site, les formules sont toujours noires, quelle que soit la couleur du texte environnant (voyez cette page, la note) ; de même sur liseuse, où le problème encore plus gênant pour les gens qui utilisent une liseuse avec arrière-plan foncé : les formules sont proprement illisibles ;
— l'alignement du texte mathématique sur la ligne n'est pas parfait, ni sa taille ;
— plus anecdotiquement, la police diffère de la police ambiante.
Cela entraîne par ailleurs des problèmes purement typographiques, notamment le rejet de ponctuation sur la ligne suivante quand la formule se trouve en fin de ligne (cf. le même exemple, au second paragraphe, ou la page suivante, première ligne).

Je souhaiterais donc voir rendues les formules de manière plus cohérente avec le texte ambiant, et de façon surtout à ne plus enfreindre les plus élémentaires règles de la typographie.

  • Qui en bénéficierait: Tous les lecteurs de textes scientifiques, et notamment ceux qui les exportent à partir de Wikisource.
  • Solution proposée: Pour l'affichage sur site web : des solutions, comme MathJax par exemple ? Pour l'export : on pourrait proposer plusieurs options d'export, l'une qui conserverait l'état actuel, avec conversion en image des formules ; une autre avec export de la syntaxe TeX directement (bien rendue sous Calibre par exemple) ; etc.
  • Autres commentaires: Bien noter que la demande ne concerne pas la saisie des mathématiques par les contributeurs, mais leur affichage et leur export.
  • Tâches sur Phabricator:
  • Proposant: ElioPrrl (talk) 18:25, 23 November 2020 (UTC)

Discussion[edit]

Allow creating bibliographic entries with the Citoid tool in VE

Edit proposal/discussion

  • Problem: Only references can be created with Citoid in the Cite tool VE, not bibliographic entries (same as a reference, but without the ref-tags). Currently these entries have to be written either manually or by cheating the Cite tool to produce the entry and removing the ref tags manually. This is beyond what can reasonably be expected from new editors.
An example of a bibliographic entry can be seen for example in this German Wikipedia article under the section "Literatur" whereas the references are created inside the text and displayed in the "Einzelnachweise" (References) section.
The Literature section does not seem to be common in the English Wikipedia, but it is very common in many other language Wikipedias.
  • Who would benefit: All Wikipedia editors, especially editors using VE primarily.
  • Proposed solution: Allow an option in the Cite tool to omit referencing or place the option somewhere else in the editing interface where it makes most sense.
  • More comments:
  • Phabricator tickets:
  • Proposer: Susanna Ånäs (Susannaanas) (talk) 09:12, 21 November 2020 (UTC)

Discussion[edit]

Bien définir les noms et les prénoms pour ne pas faire d'erreur dans les éphémérides

Edit proposal/discussion

  • Problème:
  • Qui en bénéficierait:
  • Solution proposée:
  • Autres commentaires:
  • Tâches sur Phabricator:
  • Proposant: Maleine258 (talk) 14:10, 24 November 2020 (UTC)

Discussion[edit]

  • @Maleine258: Salut! Pourriez-vous s'il vous plaît remplir le formulaire ci-dessus, tel que le "Problème" et "Qui en bénéficierait"? Ce que vous proposez ne ressort pas clairement du titre. Merci! MusikAnimal (WMF) (talk) 01:44, 25 November 2020 (UTC)

Suivi que d'une partie d'un article

Edit proposal/discussion

  • Problème: Pouvoir suivre qu'une partie d'un article
  • Qui en bénéficierait: Tous les utilisateurs de Wikipédia
  • Solution proposée: Ajouter un lien de suivi au niveaux des sections de l'article
  • Autres commentaires: Sur des articles très long et souvent modifiés par les contributeurs, il est nécessaire de visualiser toutes les modifications effectuées les unes après les autres, afin de visualiser les changements intervenus dans les sections qui m'intéressent.
  • Tâches sur Phabricator:
  • Proposant: --13:47, 25 November 2020 (UTC)Thierry74 (talk)

Discussion[edit]

Most między serwerem Discord i kanałami IRC

Edit proposal/discussion

  • Problem: Społeczność wikipedystów na platformach Discord i IRC jest rozdzielona.
  • Kto zyska: użytkownicy IRC oraz Discord
  • Proponowane rozwiązanie: Wykorzystanie bota do stworzenia połączeń między platformami komunikacji.
  • Dalsze informacje: Komunikowanie się z osobami na serwerze Discord bez zakładania konta na tej platformie jest niemożliwe, nie ma też oficjalnej możliwości na użycie innej aplikacji klienckiej. Korzystanie z IRC nie jest tak przyjazne dla nowych użytkowników, lecz jest otwartym standardem, dzięki czemu każdy może korzystać z wybranej przez siebie, dowolnej aplikacji klienckiej, na dowolnej platformie i urządzeniu. Połączenie platform sprzyja współpracy między użytkownikami z różnymi możliwościami i preferencjami, co przekłada się na zwiększenie dostępności. Rozwiązania stosujące boty do połączenia społeczności między różnymi platformami komunikacji są już stosowane na serwerach niektórych projektów FOSS takich jak np. https://www.lineageos.org, https://lutris.net
  • Wątki w Pharbricatorze:
  • Proponujący: Acetylen (talk) 15:21, 25 November 2020 (UTC)

Dyskusja[edit]

Strukturieren von Einzelnachweisen

Edit proposal/discussion

  • Problem:
  • Wem würde dieser Wunsch helfen:
  • Lösungsvorschlag:
  • Weitere Kommentare:
  • Phabricator-Tickets:
  • Antragsteller: Tsor (talk) 15:47, 26 November 2020 (UTC)

Diskussion[edit]

Im Testwiki gibt es eine eine neue Option zum Strukturieren von Einzelnachweisen, mit der man auf mehrere Stellen desselben Werkes verweisen kann.

Projektseite Tsak 100645

Bitte diese Funktion aktivieren.

Antragsteller: --Tsor (talk) 15:47, 26 November 2020 (UTC)

Fixed Link to project page --Bicycle Tourer (talk) 19:43, 26 November 2020 (UTC)

Activation of this feature will finish repeated discussions about how to abbreviate similar citations with only small differences, e.g. different page numbers. Today authors are inventing special mechanisms using template:anchor, which will be very difficult to maintain in future. Thes feature could probably include a solution to the requested new feature "Re-use citations with changed page number in visual editor". It is esp. useful for power editors, who create long articles. BR --Bicycle Tourer (talk) 19:43, 26 November 2020 (UTC)

  1. REDIRECT Community Wishlist Survey 2021/Editing/Fix “NoteTag” Bug

Improve pdf outprints

Edit proposal/discussion

  • Problem: PDF does not work anymore
  • Who would benefit: Anyone who wants to use wiki in printed form
  • Proposed solution: Make PDF possible again. In older times there were two versions: text in one column including tables and text in two columns excluding tables. It would be desirable if the text could come in two columns and including tables as well as images in a suitable format (eg image (s) with text next to it in full page width). This would make the printout more "professional" in its design.

On the same occasion, the text should be corrected so that text arranged in list form (with numbers or hyphens) gets the same form as other running text (which was not the case before).

It is desirable if it becomes possible to edit a pdf layout and update the appearance until it gets the desired look prior to printing.

  • More comments: Not all people are computer geniuses, so the possibility to the ability to edit the text should be fairly simple to understand.
  • Phabricator tickets:
  • Proposer: Sven Halfdan Nielsen (talk) 07:19, 17 November 2020 (UTC)

Discussion[edit]

Comment Comment It's possible to download PDF with Chrome, but not for Firefox. We need also to do a review of this. I'm not sure if it's the same problem or one different, but apparently are related. --Ganímedes (talk) 09:48, 17 November 2020 (UTC)

@Ganímedes: can you elaborate ? It works just fine for me. —TheDJ (talkcontribs) 11:45, 17 November 2020 (UTC)

Comment Comment I'm a teacher, I sometimes use wikibooks with my students and this could be an important improvement, because they often need a good print version in order to follow properly the activities during the lesson in class. The majority of students don't have digital devices so a good print would help a lot.--AGeremia (talk) 11:04, 17 November 2020 (UTC)

@AGeremia: I would file a separate request for book rendering to PDF, as this also requires combining multiple wikitext pages into a single document, which is a complex procedure with much additional logic. Please do file that as a separate request. —TheDJ (talkcontribs) 11:45, 17 November 2020 (UTC)

Comment Comment @Sven Halfdan Nielsen: "Make PDF possible again". PDF already is possible, most wikis have a "Download as PDF" link right in the left column. Can you be more specific perhaps about where and when it does not work for you ? I also see you'd with additional layout options, which seems like a separate request from 'make pdf possible again".. —TheDJ (talkcontribs) 11:45, 17 November 2020 (UTC)

Comment CommentPDF versions could be a good choice if they did not release author private information. For more information, read this page at Wikimedia. --Doostdar (talk) 14:03, 20 November 2020 (UTC)