User talk:Verdy p

Talk archives: 2006 · 2007 · 2008 · 2009 · 2010 · 2011 · 2012 · 2013 · 2014 · 2015 · 2016 · 2017 · 2018 · 2019: Jan–Jun, Jul–Dec · 2020: Jan–Jun, Jul–Dec · 2021 · 2022 · 2023 · 2024 · 2025 · 2026–

---

For contacting me by email, please see also fr:Utilisateur:verdy_p, or use my talk page at fr:Discussion Utilisateur:verdy_p (on my home wiki): I don't want to monitor changes in all wikis, notably with emails formatted in various languages depending on the source wiki, or from unadministered small wikis harvested by spammers, or dummy "welcome" messages sent by bots). You can write me on my talk page of any Wikimedia wiki, I'll be notified from any Wikimedia wiki (because I'm connected with a SUL-enabled account) even if you can't send emails from all wikis. You should still be able to send emails from my home wiki (preferably in English or French if you can, but you should try to use some automatic online translators for your posts).
Thanks are always welcome: many users forget to do that. But this helps proving that our work is appreciated, and that we just try to do cooperatively our best on this wiki, hopefully without breaking, cancelling or blindly reverting all the patient work made by us or by others, and that some of our possible errors or disagreements can be fixed or negotiated easily, without causing major troubles with a few intolerant Wikimedia users (who forget the community rules, and "overreact" for what is a minor issue or just a disagreement of personal opinions on specific topics). There should always exist a way to coexist even in case of disagreement. So don't forget the neutrality and politeness rules of Wikimedia (see for example Category:Wikipedia policies and guidelines).
Please sign and date your posts on my talk page (so that they can also be archived correctly):
Just add four tildes ~~~~ at end of your message, and it will look like this signature (with your linked user name and the date of your new message): verdy_p (talk) 01:13, 13 June 2019 (UTC)

Category:Paganist_funerals_in_art

Paganist funerals in art 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!

DNocterum (talk) 04:38, 9 January 2026 (UTC)

Category:Paganist_funerals

Paganist funerals 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!

DNocterum (talk) 04:40, 9 January 2026 (UTC)

Category:Islands in Indonesia

Hello! I noticed that you moved this category from Category:Islands of Indonesia. Can I ask why? Because all other categories use "of <country>" format, and I'm not sure what is the reason for this inconsistency. Deltaspace42 (talk) 14:40, 10 January 2026 (UTC)

That was 4 years ago(!) apparently the naming scheme was reversed, but at that time, "Islands in country/region" were more common than "Islands of country/region", and the two categories for Indonedia were just merged; There's no problem to reverse the redirection. verdy_p (talk) 14:53, 10 January 2026 (UTC)

Okay, thanks for the reply. I'm going to move it back to Category:Islands of Indonesia to maintain consistency. Deltaspace42 (talk) 13:45, 11 January 2026 (UTC)

Make UCB symbols and pictographs extended A and supplemental Symbols and pictographs

Update miscellaneous symbols and pictographs ~2026-98159-9 (talk) 21:03, 12 February 2026 (UTC)

I'm busy since some times in reviewing the Tangut script and its composition, as part of Unicode 17.0. I know that Unicode 18.0 alpha preview is started and a few other characters will be added there. Anyway on your request I created File:UCB Symbols and Pictographs Extended-A.png (see also its talk page about how I created a snapshot PNG version from HTML with CSS and existing fonts, there will be the need to complete some new characters with SVG images, before we get updated fonts). The next block will come soon. verdy_p (talk) 23:54, 12 February 2026 (UTC)

File:UCB Miscellaneous Symbols And Pictographs.png

Fix glyphs quality ~2026-98159-9 (talk) 09:00, 13 February 2026 (UTC)

They are VERY accurate, coming from an actual serious free font (Noto Emoji). This table is NOT using color version as such table is only to show the characters in text style. But if you want I can produce a second image with Noto Emoji Color. The rendering is to match other tables in the same collection of HD tables. Nothing to do here (see File_talk:UCB_Symbols_and_Pictographs_Extended-A.png for the HTML+CSS version from which a wide screenshot was taken). verdy_p (talk) 09:04, 13 February 2026 (UTC)

coming soon in 2 hours ~2026-98159-9 (talk) 10:53, 13 February 2026 (UTC)

Fixing my categories

Whenever i make my own categories, you always fix the description. Thank you. Qawerasersa (talk) 16:36, 14 February 2026 (UTC)

@~2026-98159-9 and Qawerasersa: Once again stop adding things for Unicode versions that are still not scheduled. There's not been in formal decision by the UTC and the WG2 to allocate additional blocks or characters for Unicode 19.0. The Unicode Pipeline is just a long term development process. Only those that are approved by the UTC and "deemed appropriate for encoding" (and with a decision to enter the public review stage) are suitable. All others can be postponed (and this has happened frequently in past versions) or encoded differently, in other blocks (because other unrelated blocks took the place, or because the encodign model was still not finalized and approved, with different proposals, possibly different character counts, with more or less provisionnally assigned UCS columns). All proposals in the Unicode Pipeline take many years to complete, frequently because there's the need to get support from many experts or working groups, discuss many important issues, ambiguities, the proposed characters may be disunified, or unified as variants, so the repertoires of these proposals are very unstable.

Only Unicode 18.0 is suitable for now as it is being finalized with an open public review (where character codes and names are now fixed, even if some characters may be dropped from the final Unicode 18.0 and rescheduled to Unicode 19.0! This complex process takes considerable time to coordinate the efforts. Mixing things here in Commons just creates confusion (and in fact various blocks that you anticipated for Unicode 19.0 may not even be located where you put them, they are not even "drafts", many discussed documents contradict each other about their proposed encodings. So STOP these attempts. All that can be done in Commons is to create categories for images, but without assuming ANY UCS encoding. What you do repeatedly just creates a maintenance nightmare and many confusions, these 'invented additional encodings are fake, completely unsourced.

You've been blocked repeatedly for these fake additions, because you caused troubles to many people with these fake unsourced (and contradicting) additions. verdy_p (talk) 12:29, 15 February 2026 (UTC)

Never knew this. Thanks for telling me. Qawerasersa (talk) 20:51, 15 February 2026 (UTC)

This is explicitly written in the description at top of categories that you constantly modify: don't pretend you did not read that, and you've been warned multiple times under your previous multiple banned accounts. Do not anticipate your desires, this does NOT help any one, it just slow downs the work which is needed for reviewing and stabilizing the content, where we don't want unstable and data that can change at any time and that still don't have any stable source and multiple possible alternatives that will take years to resolve and review by independent experts working worldwide, and seeking for more information to find the best solutions and solve ambiguities, disagreement/conflicts/errors and technical problems in proposals: Unicode and ISO will only encode something that is considered stable and agreeds by their many experts and working groups, and after they both vote to approve their inclusion in the repertoire of the next UCS release, and then start preparing that release for public review. verdy_p (talk) 21:08, 15 February 2026 (UTC)

That was probably the other person, this is my only account. Qawerasersa (talk) 23:50, 16 February 2026 (UTC)

All this stuff is true Qawerasersa (talk) 14:27, 21 February 2026 (UTC)

“𠀇”

GlyphWiki just uploaded a new version of this image ! Can you replace the current version of this image with new version of this image? ~2026-11717-20 (talk) 03:15, 22 February 2026 (UTC)

I did that, but that was not really needed, these are very minor adjustment for another prefered default variant (the Chinese one, instead of Kanji that is still referenced in Glyphwiki and in Unicode charts), not even very recent. You don't need me to perform such imports if you feel it is really useful. So please don't ask me again the same thing, assume your work yourself. verdy_p (talk) 03:58, 22 February 2026 (UTC)

Cracking face “🫫” (U+1FAEB)

Could you upload Glyphwiki version of https://en.glyphwiki.org/wiki/unstable-u1faeb -- ~2026-98159-9 (talk) 19:27, 2 March 2026 (UTC)

Done (with a category and Wikidata entry), but as you see it is unstable, made for Unicode 18.0 (alpha draft). verdy_p (talk) 07:08, 3 March 2026 (UTC)

Category:Unicode 1DB00-1DBFF Miscellaneous Symbols and Arrows Extended

Why is the website link tangut supplement? Qawerasersa (talk) 12:48, 3 March 2026 (UTC)

Because there's a Tangut symbol in that block: "Tangut iteration mark" (not an ideograph and not a Tangut component) and it's not in the Symbols supplement block you weakly indicated! verdy_p (talk) 12:49, 3 March 2026 (UTC)

Beware, there's a recurring abusive user (permanently blocked) that is still causing havoc (using anonymized temporary IP connections, without account) and inventing additions about Unicode and many scripts, on Commons and multiple editions of Wikipedia or Wikitionary, inventing characters, pretending they are standard, changing their history (including notably in wellknown scripts like Greek or Cyrillic, but as well inventing Latin characters, making false representations of their properties or usages), deleting accurate sources but not adding any one for his inventions. He has been blocked in many wikis. This may explain the confusion you saw (but thanks you reverted most of its recent changes). verdy_p (talk) 13:33, 3 March 2026 (UTC)

Note that there's four Unicode blocks exclusively for Tangut (two for ideographs, two for components), but the additional symbol is in a generic block. All blocks are properly linked. verdy_p (talk) 13:40, 3 March 2026 (UTC)

I understand now: I fixed the link to the draft chart in Category:Unicode 1DB00-1DBFF Miscellaneous Symbols and Arrows Extended, which used the wrong starting codepoint, going to an Tangut draft chart update instead of the expected draft chart for the new block. Next time, please be clear about the page, include a wikilink in your message. verdy_p (talk) 14:31, 3 March 2026 (UTC)

Ok Qawerasersa (talk) 22:25, 3 March 2026 (UTC)

File:UCB Symbols and Pictographs Extended-A.png

Add support for unicode 18.0 Milan Szymon Szulc (talk) 19:56, 5 March 2026 (UTC)

I have no font available for the new Unicode 18.0 (alpha public review draft) emojis. I'll update the table when I find a suitable font for them. verdy_p (talk) 07:03, 6 March 2026 (UTC)

Add all files in Category:Unicode 3D000-3FC3F Seal. Why is the files in Seal script Milan Szymon Szulc (talk) 07:27, 8 March 2026 (UTC)

The script is being encoded in the UCS, in a new block. There are still no font available but characters exist and we already have resources for many of them in Commons. This is in preparation for many glyphs to be uploaded soon. The script is quite large, but encoded differently then CJK unified ideographs that inherited (partially) from them, with many modifications that cannot be unified with the modern CJK script. It is being encoded since many years, the proposals have stabilized, and we are nearing the time of the end of the alpha period at end of March (where the repertoire is now fixed, but glyphs are being actively reviewed, the next step will start in mid-April to set and review the final character properties, for a final publication in September). For now it is a work in progress, we have to make our own local review in Commons (just like with all other pending Unicode 18.0 additions in active review and finalization). I'm jsut preparing the structure to help the next step, effective uploads will be properly ordered and categorized with this common structure in place. verdy_p (talk) 08:10, 8 March 2026 (UTC)

Upload 𣅼-seal.svg, 昧-seal.svg, 暏-seal.svg, 昭-seal.svg Using https://hanziyuan.net/ Milan Szymon Szulc (talk) 09:12, 8 March 2026 (UTC)

Sorry if you want them, make your own work (using available data sources, with appropriate open licences). I have other goals, and do not take explicit orders to do work for your own desires or expectations, that's not the way Wikimedia works. Yes, this means passing time to search, develop, draw, test, and this requires patience and investment with your own ressources (notably in terms of time, cerebral reflection, and sometimes physical resources and money that you can donate to the project). I'm already heavily involved in the Unicode 18.0 review (but also with existing work to fix Unicode 17.0 that has not been completely reviewed, which requires also using means of contacts to document your review as precisely as possible). verdy_p (talk) 10:09, 8 March 2026 (UTC)

And please do not manage my talk archives. That's my talk pages, I archive when I want, when the talk page becomes overlong and when sufficient time has passed so that no late responses are expected. Archives of user talk pages made by others without authorization by that user are NOT welcome, they cause havoc and unjustified notifications. Your attempt is a loss of time, as I had to control what was done, by recovering from a known state; there was no emergency to archive 2025 talks in this page, archives may span irregular periods of time. verdy_p (talk) 10:47, 8 March 2026 (UTC)

I will work these Category:Seal radical 231. Milan Szymon Szulc (talk) 11:11, 8 March 2026 (UTC)

UCB Latin Extended-D.png update for unicode 18.0 file outdated Milan Szymon Szulc (talk) 15:24, 8 March 2026 (UTC)

Done. verdy_p (talk) 16:58, 8 March 2026 (UTC)

Update File:UCB_Symbols_and_Pictographs_Extended-A.png

• https://files.catbox.moe/8rlq6b.zip

I tell to add files of u18.0 in UCB Symbols and Pictographs Extended-A.png Milan Szymon Szulc (talk) 17:38, 8 March 2026 (UTC)

I cannot use external files without a valid licence. The table is generated in HTML with most accurate fonts, otherwise using some good image sources with valid licences, otherwise by manual composition in the PNG. This file has a talk page describing the source for regenrating it with the correct metrics, this HTML table can be tuned when new fonts are available (with a coherent style) to render it completely. This will come soon with Noto Emoji updates (work is pending and is already in progress to update the Noto Emoji fonts that should contain them, but for now it is not ready). You have already asked that above and I replied. There's no emergency for now for these new emojis, no one use them on any supported platforms (MacOSX, iOS, Windows; Android and Linux, as well as many social platforms have builtin support for Noto Emoji, Microsoft is quite long to update these emojis in its proprietary font that we cannot use to derive SVG images, but whose usage in isolated bitmaps embedded in documents is permitted). I don't need your zip file which just contains existing screenshots. verdy_p (talk) 17:49, 8 March 2026 (UTC)

Convert pdf https://www.unicode.org/charts/PDF/Unicode-18.0/U180-1FA70.pdf into svg and i need you to use inkscape please Milan Szymon Szulc (talk) 18:25, 8 March 2026 (UTC)

I am not building any font. Fonts are made by more talented typographs, and for Emojis, they are managed by each supporting platform, in their dedicated project (e.g. on GitHub for Noto Emoji fonts), who also decide about their apparence/style. These developers also work already in cooperation with the Unicode UTC and submit their own review, compare their work, discuss with social plaforms needing to interchange them. Emojis have a very special development; glyphs currently in the Unicode charts are very basic, and may not pass the current review. There's a Unicode PRI about this review for Emoji 18.0, which is separate from the rest of Unicode 18.0. We don't need to anticipate, there are already many serious people working on this (and get sure that we'll see updates for Emoji 18.0 very soon after the Unicode 18.0 release, provided by OS vendors and on open projects like Noto, supported by Google, the Linux Foundation, and the Wikimedia Foundation (that are already active plain members of Unicode). GitHub is already active but the early drafts for Emoji 18.0 are not suitable for now (and legally, we cannot extract someting from Unicode charts without violating the Unicode licence and terms of use; and even the use of glyphs in Unicode draft charts is not fully licenced for general use, their purpose is limited to the temporary review process). If you have comments about this you an follow the PRI 536 (main specification) and 537 (emojis) and its existing issues (https://www.unicode.org/review/pri536/ and https://www.unicode.org/review/pri537/), and you can submit also your own review on the Unicode contact form (https://www.unicode.org/reporting.html). Note that even for now the repertoire for Unicode 18.0 is not completely stable (it will be stable in May during the beta review, where essential properties will be finalized and names will be permently fixed and not reassigned to something else). There are also other sites working on Unicode 18.0 (including notably Glyphwiki for CJK related-scripts like Tangut, Jurchen, and CJK Unified Ideographs extensions). Designing new emoji glyphs are clearly not a priority for now, we can stick on the documentation and comment them, as Unicode may change the representative glyphs (this has occured frequently in the past for Emojis, while implementations and deployements in social apps progressed). verdy_p (talk) 18:41, 8 March 2026 (UTC)

download font: https://github.com/Losketch/UnicodeFontSet-magisk-module/blob/main/module/system/fonts/UFSTempAlpha.otf Milan Szymon Szulc (talk) 19:16, 8 March 2026 (UTC)

That temporary font does NOT install properly, it is probably made specifically for MacOS, or is not conforming to the OTF standard. You can preview it, partially, but the table of glyphs is broken, and probably does not have a suitable glyph mapping, or is missing the suitable licencing requirements in its metadata. Report the bug to its creator, who is likely working on it and has still not released it (its last release is for Unicode 17 only). In my opinion it failed to build properly. Before posting random links here, please test it first yourself. verdy_p (talk) 19:24, 8 March 2026 (UTC)

Redone font https://files.catbox.moe/jt14v4.ttf Milan Szymon Szulc (talk) 19:49, 8 March 2026 (UTC)

Also the "Unifont" is a poor one, made using bitmaps at low resolution. It may only be useful as a generic fallback font to display a default glyph (instead of jsut some tofu), and does not have any OTF feature required for most scripts that require these features. It's most likely the reason that the temporary build cannot be installed, but is only usable within some unspecified font editor. verdy_p (talk) 19:36, 8 March 2026 (UTC)

Stop sending fake links to non working files. Your "redone" font is worse than the last one. It is completely broken (0 bytes downloaded, filtered probably because of embedded malware: CHECK YOUR PC, it's possibly heavily infected) and does not have even any preview. Do not use temporary work fonts, especially coming from a personal GitHub fork, where the file is evidently marked as "temporary" (meaning work in progress). I would prefer using the original Unifont project, which reviews the submissions made in forks and reject many failed attempts. Once again, do your homework first, test, do not send your fast creations. And reread; Unifont is not suitable for any represenative glyph or script. It is just a fallback font with very poor bitmap resolution. I won't use it for an Unicode chart due to its poor quality and characters that are extremely hard to distinguish reliably. verdy_p (talk) 19:59, 8 March 2026 (UTC)

https://files.catbox.moe/bzq58j.png upload this for unicode 18.0 Milan Szymon Szulc (talk) 20:21, 8 March 2026 (UTC)

Once again, infected by malware. Your PC needs serious cleanup. I will no longer trust any one of your shared files from your personal cloud storage provider. Your files will be rejected as well by GitHub. Clean your PC, try forking the GitHub project you want to modify, and upload your modifications in your GitHub fork. You'll see waht GitHub will reply you, it will reject your uploaded files as long as you've not cleaned up your working environment and secured it. If you can't clean it, try making a backup of your own data files on a separate drive (but they may already be infected), and make a full clean reinstallation of your OS and all its application. Then scan and clean your backup archives before reusing them. verdy_p (talk) 20:25, 8 March 2026 (UTC)

Make UCB Latin Extended-E.png, UCB Latin Extended-F.png, UCB Latin Extended-G.png Milan Szymon Szulc (talk) 05:52, 9 March 2026 (UTC)

Please back Milan Szymon Szulc (talk) 07:51, 9 March 2026 (UTC)

Please don't send orders. I have other things to do, and there's no emergency. I perfectly know that these images are msising in the related category, and there are others (already listed there); recently I made Cyrillic Extended-C and completed a few others. Note: do not use "F" templates in section headers, they break the navigation with incorrect anchors from the TOC or after editing messages. verdy_p (talk) 08:32, 9 March 2026 (UTC)

Update File:UCB Transport and Map Symbols.png for outdated Milan Szymon Szulc (talk) 09:12, 9 March 2026 (UTC)

Update this file for unicode 18.0 https://files.catbox.moe/yatoi7.png Milan Szymon Szulc (talk) 09:48, 9 March 2026 (UTC)

I won't use files from your untrusted private storage, given the security issues you have on your PC, very likely infected by malwares as demosntrated above. Also I don't need any one of your files (I trust the existing Noto source repository on GitHub for that collection of glyphs). verdy_p (talk) 09:54, 9 March 2026 (UTC)

edit: but upload without catbox.moe Milan Szymon Szulc (talk) 10:09, 9 March 2026 (UTC)

I just tell to upload Milan Szymon Szulc (talk) 10:53, 9 March 2026 (UTC)

I've used "Noto Emoji" for Unicode 17.0, and manually drew the additional LIGHTHOUSE character (U+1F6D9) for Unicode 18.0. verdy_p (talk) 11:11, 9 March 2026 (UTC)

Upload symbols and pictographs extended a for unicode 18.0

using files [https://private-user-images.githubusercontent.com/141835174/560459844-2480e5fe-f945-443b-a0ec-2a33c358d15e.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzMwNzkxNDAsIm5iZiI6MTc3MzA3ODg0MCwicGF0aCI6Ii8xNDE4MzUxNzQvNTYwNDU5ODQ0LTI0ODBlNWZlLWY5NDUtNDQzYi1hMGVjLTJhMzNjMzU4ZDE1ZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMzA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDMwOVQxNzU0MDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05OWYyZjc0N2E1MjJiZjEyYWIyOTM2ODFlMmNjYWY4ODBjNWU4N2IyMjBkODk4YzE2NzYzODJkNzUwYjI3NmFiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.vmQHi1Zto4NECdtoR1wii8JBKYiLIwzryt_mZERI7DM text], [https://private-user-images.githubusercontent.com/141835174/560459862-2f4372ff-d8a7-4152-aba8-11390fbcc816.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzMwNzkxNDAsIm5iZiI6MTc3MzA3ODg0MCwicGF0aCI6Ii8xNDE4MzUxNzQvNTYwNDU5ODYyLTJmNDM3MmZmLWQ4YTctNDE1Mi1hYmE4LTExMzkwZmJjYzgxNi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMzA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDMwOVQxNzU0MDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zOTk5MTkzY2RhNmEwNDRhZjk5YTA1NWExYTgyMGM4YTI2NGQ4ZTc3Yzk5NzVjZGU5ZmQyNjVmYTY3OTM4MDU0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.Ar5ZuTy9IzyOIDJ6GRiMgrtqSGblwnmznVH4b-mqi4g color] Milan Szymon Szulc (talk) 17:55, 9 March 2026 (UTC)

please back Milan Szymon Szulc (talk) 18:17, 9 March 2026 (UTC)

The text version is already done and complete for Unicode 17&18 and your links are invalid (error 404, they were deleted by GitHub, probably infected by malwares, or GitHub does not allow to share these "private" images without a strong authentication with your account, your files were rejected there; once again, cleanup your PC, reinstall your OS completely!). verdy_p (talk) 18:53, 9 March 2026 (UTC)

And stop spamming this talk page with new topics for the same thing. If you continue, I'll report you for abuse and repeated harassment (in addition to your attempt to send dangerous malwares, that have for now have systematically failed, thanks to secirity measures taken by other providers and by this wiki). verdy_p (talk) 19:01, 9 March 2026 (UTC)

Update File:UCB Miscellaneous Symbols Supplement.png. Fix U+1CEF1-EFD Milan Szymon Szulc (talk) 20:27, 9 March 2026 (UTC)

Please back Milan Szymon Szulc (talk) 05:05, 10 March 2026 (UTC)

Add files from Category:Noto Emoji 17 Files upload link: github.com/googlefonts/noto-emoji Milan Szymon Szulc (talk) 15:27, 10 March 2026 (UTC)

I have already Noto Emoji 17, they were already used in those charts you mentioned earlier. I have also included one new Unicode 18 glyph (for the lighthouse) in one file in the precedent thread. So nothing else to do for now, and I'm busy on something else, you don't "help"me at all here. I really wonder how you perform your checks... Anyway I know that there are other chart files to update, and I do that when I have time, in my own schedule, don't send orders, I'm not at your service. verdy_p (talk) 16:08, 10 March 2026 (UTC)

make file of ucb symbols and pictographs supplemental and color Milan Szymon Szulc (talk) 18:09, 10 March 2026 (UTC)

Fix File:UCB Geometric Shapes Extended.png. Remove cat-a-lot Milan Szymon Szulc (talk) 19:47, 10 March 2026 (UTC)

What??? It's nowhere in wiki pages (except in your preferences): this is a standard optional gadget, used by lot of users. verdy_p (talk) 21:57, 10 March 2026 (UTC)

Make UCB Sidetic, UCB Old North Arabian, UCB Manichaean and more brahmic scripts Milan Szymon Szulc (talk) 05:22, 11 March 2026 (UTC)

I know that, this is waiting for long in the category listing the HD tables. But there's still no emergency. Stop sending orders. I have more urgent things to do, espcially for the Unicode Consotirum that has instructed me to progress as fast as possible on the Unicode 17.0 review where I have already sent issues. nicode and the Script Ad Hoc Commitee are waiting a comprehnesive reports on large ideographic scripts that have lot of issues notably in the Unicode 17.0 review that was not finalizedwhen it was released last year (this comes even before Unicode 18.0, we have more time). Small scripts or extensions of wellknown scripts don't have severe issues. verdy_p (talk) 08:01, 11 March 2026 (UTC)

optimize File:UCB Alchemical Symbols.png Milan Szymon Szulc (talk) 16:08, 11 March 2026 (UTC)

I remade the snapshot of the HTML table with a complete updated font, making precise capture at full resolution (this requires assembling captures vertically in an image editor, keeping metrics), ensure it was purely back&white with no color fringes, and saved with a better PNG compressor, preserving all details. verdy_p (talk) 19:05, 11 March 2026 (UTC)

Fix size File:UCB Alchemical Symbols.png Milan Szymon Szulc (talk) 07:01, 12 March 2026 (UTC)

Why are you making requests mine??? Milan Szymon Szulc (talk) 07:13, 12 March 2026 (UTC)

What? you even pretend in a revert that you optimized it, when in fact the metrics were not correct, you recorrected it, and the optimization was lost. I don't understand what you mean just in "Why are you making requests mine?" which makes no sense. And why then do you need to repost this thread? you don't need to spam here the same request with the same message heading, you just pollute this page. verdy_p (talk) 17:26, 12 March 2026 (UTC)

HTML table request for File:UCB Bamum.png, File:UCB Meetei Mayek Extensions.png, File:UCB Coptic Epact Numbers.png, File:UCB Old Permic.png, File:UCB Osage.png, File:UCB Sidetic.png, File:UCB Old North Arabian.png, File:UCB Manichaean.png and File:UCB Miscellaneous Symbols and Arrows Extended.png Milan Szymon Szulc (talk) 19:25, 12 March 2026 (UTC)

Can you add unicode 18.0 characters into File:UCB_Armenian.png Qawerasersa (talk) 22:58, 12 March 2026 (UTC)

improve glyphwiki seal

https://en.glyphwiki.org/wiki/unstable-u3d001 弌

https://en.glyphwiki.org/wiki/unstable-u3d002 元

https://en.glyphwiki.org/wiki/unstable-u3d003 天

https://en.glyphwiki.org/wiki/unstable-u3d004 丕

https://en.glyphwiki.org/wiki/unstable-u3d005 叓

https://en.glyphwiki.org/wiki/unstable-u3d006 丄

https://en.glyphwiki.org/wiki/unstable-u3d007 𠄞

https://en.glyphwiki.org/wiki/unstable-u3d008 上 Milan Szymon Szulc (talk) 20:54, 14 March 2026 (UTC)

Update these

Sorry for all the requests, but can you make all ucb unicode photos into unicode 18.0? Qawerasersa (talk) 12:26, 16 March 2026 (UTC)

When I have time for that! I know what I have to do and what is missing, don't ask me to change my ongoing work. And I'm not paid, I do that along many other things (on this site or elsewhere, or just in my personal life at home, with friends, or to prepare a theater show with repetitions, or take a few days of vacations, or have medical rendez-vous, or prepare food, cleanup my house, various garden activities, listening music, looking at TV or films... And of course I need to sleep. No one can ask me the same times every few hours and insist. I do my best in my own ordered schedule. And I evaluate myself what is more urgent, or can be completed the most easily, or what can be prepared in advance, to ease the completion tasks later, facilitate checking, and to limit posible errors or and duplicate review work that will also waste my limited time. verdy_p (talk) 12:43, 16 March 2026 (UTC)