User talk:Verdy p

Category:Russia at the 2024 Winter Youth Olympics[edit]

Russia won't compete at the 2024 Winter Youth Olympics, therefor you could delete this category. Didn't think it would need a delete request so I messaged you this way. Florian100100 (talk) 13:42, 15 January 2024 (UTC)[reply]

Category:Winter_in_the_Northern_Hemisphere_by_year[edit]

Winter in the Northern Hemisphere by year has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this category, please note that the fact that it has been proposed for discussion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category.

In all cases, please do not take the category discussion personally. It is never intended as such. Thank you!

čeština ∙ Deutsch ∙ English ∙ español ∙ français ∙ italiano ∙ magyar ∙ Nederlands ∙ português ∙ polski ∙ sicilianu ∙ slovenščina ∙ Tiếng Việt ∙ беларуская (тарашкевіца) ∙ македонски ∙ русский ∙ українська ∙ ತುಳು ∙ ಕನ್ನಡ ∙ ไทย ∙ עברית ∙ 日本語 ∙ 中文 ∙ +/−

OmegaFallon (talk) 16:26, 13 February 2024 (UTC)[reply]

Modification du modèle Lang gallery[edit]

Bonjour,

On dirait que votre modification a brisé l'affichage des traductions intégrées -- voir la page Conic Sections.svg, par exemple.

Cordialement, Iketsi (talk) 23:25, 19 February 2024 (UTC)[reply]

C'est un bogue non pas des modèles, mais du module Iteration, qui omettait de mettre un saut de ligne entre deux images de galeries; le code générait la liste des "nom de fichier|description" sur une seule ligne concaténée, ce qui n'affichait alors qu'un seul fichier dans la wiki-balise "gallery" générée. J'ai eu du mal à trouver la cause, visiblement ce qui avait changé c'est que l'expansion du sous-modèle ne générait pas de saut de ligne à la fin, c'était "trimmé" maintenant par Scribunto. J'ai du rajouter un saut de ligne explicite dans le module après chaque fichier énuméré dans le contenu de la balise "gallery". verdy_p (talk) 09:57, 20 February 2024 (UTC)[reply]

Génial! Iketsi (talk) 02:58, 25 February 2024 (UTC)[reply]

Modification des modèles Tincture[edit]

Bonjour Verdy p,
Vous avez apporté des modifications au modèles Tincture, Tincture draw, ainsi qu'à Template:Tincture/styles.css
Comme vous pouvez le voir sur la description de ce blason, par exemple, la valeur de hauteur de ligne, ainsi que la taille des caractères, probablement, dans la section "couleur", sont désormais légèrement trop élevées par rapport autres sections contenant du texte…
Serait-il possible de revenir à une valeur moindre, au moins pour les blasons ?
Cordialement,--Kontributor 2K (talk) 19:31, 3 March 2024 (UTC)[reply]

Comme je ne peux pas le voir justement. Je ne vois pas en quoi c'est plus élevé. Alors qu'aurapavant les titres de noms de couleur débordaient des cases, ce qui ne se produit plus du tout (quelque soit le zoom actuel du navigateur ou ses polices par défaut). Là c'est on ne peut plus standard, et toutes les cases de couleur s'alignent parfaitement (y compris quand il y a des sauts de ligne quand les cases de couleurs ne tiennent pas toutes sur la même ligne, elles forment une grille parfaite. J'ai aussi testé avec les options d'accessibilité qui maintenant sont également conformes. Je ne vois strictement aucune anomalie sur le blason de Grasse que tu veux citer en exemple.

Franchement si tu as une capture d'écran et si tu précises ton OS et ton navigateur, on pourrait comprendre. Mais J'ai bien peut que ce sont ton navigateur qui soit très obsolète ou mal configuré, ou l'effet d'un skin personnalisé spécifique à toi dans tes préférences, ou alors ton cache dans ton navigateur qui est corrompu. verdy_p (talk) 23:40, 3 March 2024 (UTC)[reply]

Je n'ai pas de problème de navigateur(s), ni de cache, pas non plus de problème de vue.

J'utilise Vector "ancienne version 2010", j'ai testé les autres skins : c'est idem avec Vector 2022, ça passe mieux en Minervaneue et Timeless (qui ont des typos plus grandes), et c'est pire avec Monobook (l'inverse). Ça passe vraiment bien en "Timeless".

Après, je pensais que tu pouvais facilement revenir en arrière pour comparer

S'il ne s'agit que de passer le line-height de 20 à 18px dans le css, je peux comparer moi-même

Après je vois que la typo par défaut a été passée en "Segoe UI", qui n'est pas vraiment websafe

Il va de soi que pour moi c'est toujours en Verdana

--Kontributor 2K (talk) 11:33, 4 March 2024 (UTC)[reply]

Le Verdana est bien trop large, alors que les polices UI (Segoe ou Noto) sont faites pour l'affichage. Les polices sont par défaut avec un line-height à 20px (avec l'interlignage à 1.4 par défaut, ça donne une taille de police supérieure. Et c'est valable aussi bien avec Vector ancienne version 2010 que nouvelle version. Minarvaneue est une niche rarement utilisée et mal testée un peu partout, et Timeless est obsolète et n'est plus mis à jour depuis longtemps, les deux ayant des problèmes d'accessibiltié et d'internationalisation (sachant qu'on est ici dans un cadre de traduction, où des libellés peuvent être affichés en arabe et chinois: il ne faut pas réduire trop et en tout cas ce n'est PAS plus grand que le reste du texte autour mais très légèrement plus petit pour tenir compte de la fine bordure de 1px autour des boites de couleur...). verdy_p (talk) 12:28, 4 March 2024 (UTC)[reply]

La question de la typo est surtout websafe ou non

Suite à la dernière modif la hauteur de ligne est ok, mais la typo encore un peu grosse, je vais tester à 11, ce qui semble quand même être plus proche de la taille de la typo du texte autour

Je ne sors pas des skins par défaut, et les tests doivent être faits, selon moi également, non loggé, pour voir tel que voit n'importe quel internaute non inscrit.

Après ce qui est bien sur un skin l'est moins sur un autre… idéalement il faudrait que les boîtes couleurs s'adaptent aux skins (typo+line-height)… mais ça ne concerne effectivement que les utilisateurs inscrits, et est donc sans objet, en un sens.

Je passe la typo à 11px, je te laisse revenir dessus si problème.

--Kontributor 2K (talk) 12:56, 4 March 2024 (UTC)[reply]

hard redirects of categories[edit]

Hi. Please do not put in hard redirects for categories, the accepted practice locally is to use {{Category redirect}} alone. The hard redirects cause issues for use of HotCat and especially problematic when categories are again redirected they are getting lost. Happy to hear what you believe is the solution that hard and soft redirects on the same page is resolving. Thanks. — billinghurst sDrewth 22:05, 6 March 2024 (UTC)[reply]

This redirect is needed for some nav templates to work correctly without forcing users to follow another link). HotCat and similar do NOT need it, and uploaders do not use this category but follow the redirect. If ever the category gets some files, it is still tracked by the soft redirect template in a tracking category so this is not an issue at all. I have made sure when putting the hard redirect at top that these categories were empty and your revert has no effect except embarrasing visitors. verdy_p (talk) 07:56, 7 March 2024 (UTC)[reply]

We should be fixing the nav templates, not putting in hard redirects. We don't make problematic fixes for problems that should be fixed at source. Hard redirects do prevent HotCat from working in that the lookups don't work for what should be the soft redirects. We are also having issues that hard redirects go to soft redirects. I doubt that any user would be embarrassed by landing at a soft redirect. — billinghurst sDrewth 04:07, 10 March 2024 (UTC)[reply]

These templates cannot always be fixed. HotCat should recognize both types (this is a bug of HotCat, not me), including simultaneously. verdy_p (talk) 01:56, 15 March 2024 (UTC)[reply]

Please stop populating Category:Category pages with broken file links‎[edit]

Your edits of putting non-existent files onto category pages is populating Category:Category pages with broken file links‎. If you wish to build galleries of images, and with missing and hoped for images, then please use the main namespace, which is the place for galleries. There is neither a need nor a requirement to be building galleries on category pages, in fact that is pretty much an antithesis of galleries and their purpose. Thanks. — billinghurst sDrewth 01:42, 25 May 2024 (UTC)[reply]

I am filling these categories coherently. You just break this work. Nothing gets broken by these. Stop your reverts of my edits there, which are all correct. These are NOT galleries but navigation.

Even if there are "missing files" reported, this is on purpose for these pages (and documented in projects). verdy_p (talk) 01:44, 25 May 2024 (UTC)[reply]

Note: it is not possible to use "ifexist" there, it does not work in the few categories where there are too many missing files (we exhaust the limit on the number of costly parser function calls). Showing red links for missing files in that case is the best option available: dropping the navbox will not solve the maintenance problem, even if the maintenance Category:Category pages with broken file links‎ is no more populated, it will just hide the problem). The navbox contains the necessary links and ensure coherent naming for missing files. I am not building any "gallery" here; this is exactly how the category pages should be, and I made sure they are minimalist. verdy_p (talk) 01:59, 25 May 2024 (UTC)[reply]

Olympic teams[edit]

Hello Verdy p, I just created Category:Southern Rhodesia at the 1928 Summer Olympics. At the top of that page neither Southern Rhodesia nor Rhodesia is showing up. It looks like the Module:Countries/Olympic teams has to do with it. I have no idea how to fix this but I noticed you sometimes were editing that page. I hope you can help me here. - Robotje (talk) 07:33, 25 May 2024 (UTC)[reply]

I know, some users created the category which is detected and displayed, because Rhodesia existed as a former delegation. I have the project to implement a filter by years in the infobox, to remove the non-relevant years. Note also that there are probably other missing historic "delegations" (in Olympics, they are not really "countries"). Byut it requires checking the correct name of the delegation (in early Olympics, various national teams were competing in mixed teams). verdy_p (talk) 07:51, 25 May 2024 (UTC)[reply]

Well, it would be nice if it is eventually fixed. It is not urgent, certainly not if there are more minor issues like this in that module. Should I add some remark on that related talk page so it stays on the 'radar'? - Robotje (talk) 08:02, 25 May 2024 (UTC)[reply]

In 1928 (and later in 1960-), "Southern Rhodesia" participated as the "Rhodesia" delegation [RHO]. The template has no problem to display it. Your category is renamed. verdy_p (talk) 08:06, 25 May 2024 (UTC)[reply]

I see it is now fixed, thanks. - Robotje (talk) 08:08, 25 May 2024 (UTC)[reply]

I will fix later the spurious occurences, like Bohemia in 2024 for example (which is displayed because it was created as a redirecting category). To implement the filter in the module requires some adjustment ni the Lua code, so that the template can take a filtering parameter (for event years, or for and event type: [Summer/Winter] [Youth] Olympic/Paralympic) that some detected delegations need to match to be effectively displayed (filters to implement are documented and those former/special delegations already have visible notes in the rendered infobox, so it still makes sense for readers that those entries are not relevant; I think it will be an additional entry in the data module used by the template, which already contains the notes but notes cannot be processed easily, so the additional optional filter data will probably be some sequence of Lua patterns). Then when using the template in category pages by year, we'll just need to pass the values (year, event type) to be matched by the filters for these former or special delegations. This is not dramatic and there are more urgent things to do (I won't break the code for now, such modification of the Lua code requires some extensive testing). verdy_p (talk) 08:31, 25 May 2024 (UTC)[reply]

At Category:Rhodesia at the 1928 Summer Olympics I already noticed something weird was going on with Bohemia but I decided not to mention another issue next to the Rhodesia one. If that Bohemia issue can be fixed one day, that would be nice. Slowly on things get better, like your fix for Rhodesia and my addition of all the missing categories for countries that participated in the 1928 Olympics. Your work in things like that is appreciated.- Robotje (talk) 09:08, 25 May 2024 (UTC)[reply]

As I said, the "weird" display of Bohemia, Czechoslovakia and Yugoslavia (not wrong from a modern view perspective, but unnecessary in that year as these are not official names of effective delegations) will be fixed later once the Lua module can support filters (that will allow eliminating the displayed links to redirected pages). This does not cause lot of pollution in the displayed list as these former and special delegations are in a small sublist at end, and are all visibly annoted. They just exist because some users created "unnecessary" redirects (or possibly these pages were initially created with the wrong name, and were moved to fix the effective name, but still keeping the old names displayed). verdy_p (talk) 09:15, 25 May 2024 (UTC)[reply]

Note also that this later fix to implement filter will be generic, and also solve some other "weird" displays of former countries or territories (not relevant in all years, if the listed categories are specific to a year) in other similar infobox, such as former Countries of Africa/Europe (by year), or former regions and departments of France, or former dependencies). Is is not specific to Olympics/Paralympics. Filters will be added with a basic parameter in categories needing them, without using historic weird parameters, like "simple=yes" which is kept but insufficient and not selective enough. These navboxes will then be smarter. verdy_p (talk) 09:30, 25 May 2024 (UTC)[reply]

Help:Namespaces[edit]

Please build your gallery pages in the main namespace, not the category namespace, per the instruction. You are creating errors for unlinked files and you are inhibiting the clean up this process when you keep repopulating. Categories are for the categorisation, not the curation of a gallery. Thanks. — billinghurst sDrewth 11:40, 27 May 2024 (UTC)[reply]

I am not building any gallery. These are navboxes in progress, the red links for missing files are there on purpose (for maintenance exactly), the navboxes you removed show also the link to the project that documents everything. See the discussion already 2 sections above. Your reverts just break ongoing work without solving ANY maintenance problem (it just hides them). I am NOT ignoring problems, but you want to hide them. Such maintenance category is there for purpose: maintenance is not just eliminating red links on files: there are works to do (and the work to do here is not the subject of any galery).

You reverts are also abusive when you maintain an administrative lock on these, without offering any help on the topic: you just block that work which is NOT stalled at all. There are other maintenance to do elsewhere than just trying to empty a category with arbitrary pseudo-solutions that offers no help, and when you replace them also abusively with INCORRECT links at top of categories (not to the correct project pages or categories). These boxes are there for proper categorisation of files (including missing ones) and they describe the content of the categories, what is expected there for their completeness and correctness (notably because the characters in question have confusable encodings, which is also patiently being documented and disambiguated). verdy_p (talk) 17:55, 27 May 2024 (UTC)[reply]

Modification Module:Iteration[edit]

Bonjour Verdy p,
Me revoici,
Il y a un souci qui est apparu, à la suite, possiblement, de modifs sur le Module:Iteration, ou autre,
(Je vois sur la page de ce module :
« 10. {{Attribs}}
The template works, whether there is a user assigned for a file, or one filename follows another. »)
Le problème apparu est avec le {{Attribs}}, justement, qui ne fonctionne plus…
Exemple sur ce fichier où il apparaît désormais dans la partie Description : Ce blason contient des éléments de « no name » et le fichier a été mis dans Category:Commons:Missing file name in template F
À noter que curieusement, tant que la page du fichier n'a pas été modifiée, (edit : ou pour une autre raison), le fichier cible voit toujours le lien, et que le fichier source se contente d'afficher le « no name » sans toutefois être catégorisé dans Missing file name in template F (bien qu'il affiche la catégorie en bas de la page) - exemple : le fichier Meuble héraldique hêtre arraché.svg contient le code {{Attribs|Meuble héraldique tilleul arraché.svg}}, fichier cible qui lui se voit bien encore utilisé par le fichier Meuble héraldique hêtre arraché.svg (dont la page n'a pas été modifiée, donc).
On peut voir par ailleurs sur la page du tilleul (cible) qu'il est utilisé par d'autre fichiers, via {{Attrib}} (sans le s), ce qui là, en revanche, fonctionne.
Le catégorie Missing file name in template F risque de se remplir progressivement…
Cdlt,--Kontributor 2K (talk) 8:45, 28 May 2024 (UTC)

That's my fault for Attribs, I documented the parameters for the subtemplate used "Atttrib" but started numbering them at 0 instead of 1, and then based that to perform the invokation; numbered parameters were offseted by 1 (starting by a parameter "0" which should not be there), this is fixed. verdy_p (talk) 14:02, 28 May 2024 (UTC)[reply]

Thank you,

I'm currently purging image-caches on CoAs, it should be back to normality soon…

--Kontributor 2K (talk) 14:08, 28 May 2024 (UTC)[reply]

I've cleaned a few ones just with null edits. So this should come back soon to normal if this categorisation occured automatically. If not, check in a few days if manual null edits are needed (in some cases, this is effectively incorrect usage of templates, you need to look at history and edits to see what is wrong, sometimes this is caused by broken edits or spams that need to be reverted, or by people that don't know how to use templates correctly and that need some help to fix their code).

Note that "Attribs" does not support any URL for indicating external source images, and filenames and usernames must not contain any "/". In that case, you need to extract those external sources from the template invokation, and place them after (in some bulleted list inside the "|Source=" parameter of the "Information" template). If there's any URL with a "/", the parameter is split in two parts after the 1st "/", the first one assumed to be a "filename" and the second one being a user name (possibly as a wikilink): the result is not meaningful. Normally filenames on Commons should not contain any "/", but user names may include one in a wikilink (such as his gallery page, or some project page on Commons or another wiki). The handling of "/" by templates Attribs and Attrib is a hack. verdy_p (talk) 14:40, 28 May 2024 (UTC)[reply]

Personnellement je ne mets pas de caractères interdits dans les modules ou ailleurs, et je m'assure généralement que tout fonctionne.

C'est un peu lent à revenir, malgré les purge, je laisse les 11 blasons tels quels, pour voir

Sinon, supprimer / remettre le Attribs fonctionne…

--Kontributor 2K (talk) 14:58, 28 May 2024 (UTC)[reply]

Un "null edit" suffit en général. Pour d'autres ce sont les paramètres dans le mauvais ordre ou avec le mauvais numéro de paramètre pour indiquer le fichier ou l'utilisateur (par exemple dans les "retouches" signalées). Dans d'autres cas, les paramètres sont dans le bon ordre, mais le nom de fichier est partiellement URL-encodé, et pour avoir le bon nom, il faut le copier-coller hors du modèle et le mettre dans un wikilien "[[:File: ... ]]" pour voir ce nom à remettre à la place (et voir en même temps s'il existe bien). verdy_p (talk) 15:00, 28 May 2024 (UTC)[reply]

User talk:Verdy p

Contents

Category:Russia at the 2024 Winter Youth Olympics[edit]

Category:Winter_in_the_Northern_Hemisphere_by_year[edit]

Modification du modèle Lang gallery[edit]

Modification des modèles Tincture[edit]

hard redirects of categories[edit]

Please stop populating Category:Category pages with broken file links‎[edit]

Olympic teams[edit]

Help:Namespaces[edit]

Modification Module:Iteration[edit]

Navigation menu

User talk:Verdy p

Category:Russia at the 2024 Winter Youth Olympics[edit]

Category:Winter_in_the_Northern_Hemisphere_by_year[edit]

Modification du modèle Lang gallery[edit]

Modification des modèles Tincture[edit]

hard redirects of categories[edit]

Please stop populating Category:Category pages with broken file links‎[edit]

Olympic teams[edit]

Help:Namespaces[edit]

Modification Module:Iteration[edit]

Navigation menu

Search