User talk:Wargaz

Welcome to Wikimedia Commons, Wargaz!

Afrikaans | Alemannisch | asturianu | azərbaycanca | Bahasa Banjar | català | čeština | Cymraeg | dansk | Deutsch | Deutsch (Sie-Form)‎ | English | español | Esperanto | euskara | estremeñu | français | Frysk | galego | hrvatski | Bahasa Indonesia | interlingua | Interlingue | íslenska | italiano | Kiswahili | Kurdî | Latina | lietuvių | magyar | Bahasa Melayu | Mirandés | Nederlands | norsk bokmål | occitan | Plattdüütsch | polski | português | português do Brasil | română | rumantsch | Scots | shqip | sicilianu | slovenčina | slovenščina | Basa Sunda | suomi | svenska | Tagalog | Türkçe | vèneto | Tiếng Việt | Zazaki | Ελληνικά | беларуская | беларуская (тарашкевіца)‎ | български | Ирон | македонски | нохчийн | русский | српски / srpski | тоҷикӣ | українська | ქართული | Հայերեն | नेपाली | भोजपुरी | मराठी | हिन्दी | অসমীয়া | বাংলা | தமிழ் | മലയാളം | සිංහල | ไทย | ၽႃႇသႃႇတႆး  | မြန်မာဘာသာ | 한국어 | 日本語 | 中文 | 中文（台灣）‎ | 中文（简体）‎ | 中文（繁體）‎ | 粵語 | עברית | اردو | العربية | تۆرکجه | سنڌي | فارسی | +/−

First steps tutorial Our first steps tour and our frequently asked questions will help you a lot after registration. They explain how to customize the interface (for example the language), how to upload files and our basic licensing policy (Wikimedia Commons only accepts free content). You don't need technical skills in order to contribute here. Be bold when contributing and assume good faith when interacting with others. This is a wiki. Getting help More information is available at the community portal. You may ask questions at the help desk, village pump or on IRC channel #wikimedia-commons (webchat). You can also contact an administrator on their talk page. If you have a specific copyright question, ask at the copyright village pump.

Goodies, tips, and tricks Put Babel boxes on your user page so others know what languages you can speak and indicate your graphic abilities. You can find the files you have uploaded in your Uploads. Please sign your name on Talk pages by typing ~~~~. To link to an image page without embedding the image, type: [[:File:Foo.jpg]], which produces: File:Foo.jpg. You may enable gadgets (custom features) for your account. There are several tools to upload files. Have you edited Wikipedia before? This guide might be useful. Made a mistake? Do you want to have a file renamed or moved? Use the move link and wait for an authorized user to rename it. Do you want to have your recently uploaded picture removed? Tag it as {{speedy|reason here}}. For more information read the deletion guidelines.

-- Wikimedia Commons Welcome (talk) 15:12, 15 April 2015 (UTC)[reply]

The new file you uploaded is basically a duplicate of File:㝵-oracle.svg. I think it should be reverted to the previous version, which is also found in the oracle bone script. Justinrleung (talk) 06:05, 24 November 2017 (UTC)[reply]

Sure. Sorry I overlooked that... --Wargaz (talk) 06:12, 24 November 2017 (UTC)[reply]

Hi, thanks for your work on the ancient Chinese characters project, especially your bold move of including more than one form for each category. I just have one concern about calling Liushutong forms "great seal". I've brought this up with User:Micheletb before, but it didn't really go anywhere. It really bothers me that we are calling anything from Liushutong "great seal". First of all, Liushutong is a collection of various styles of seal inscriptions, not necessarily specific to any era. Second of all, "great seal" could mean anything before the small seal script, so the name itself is kind of an umbrella term for the oracle bone script, bronze inscriptions and other scripts around the same era. What are your thoughts on this? Should we even keep these as "great seal", or should we rename them to "Liushutong" forms? Justinrleung (talk) 07:48, 28 December 2017 (UTC)[reply]

I certainly agree with you. Great seal is an ambiguous term which was already abandoned by mainstream Chinese grammatology. It would be better if scripts from Liushutong have their own category. I personally prefer the categories of Xiaoxuetang, and those scripts from Liushutong may under the category of "transcribed (chuanchao) ancient scripts". For example, the "great seal" of 高 is pretty much identical to several transcribed ancient scripts from Xiaoxuetang. In chronological order, Shouwen was published between about 100-121 AD, and Liushutong was published about 1627–1644. The time gap between Liushutong and pre-Qin period is huge, which means scripts from Liushutong can't reflect the original graphic form of ancient scripts. Currently, Liushutong scripts are one of five priorities on the ancient Chinese characters project. I suggest that they can be put aside for a while, and Qin bamboo and slip scripts, staging of bronze scripts and categorizing of Shuowen scipts like Zhou, Ancient and Odd can be added to the Han etym template. Qin bamboo and slip scripts are one of newly emerged subjects of ancient Chinese characters along with Chu bamboo and silk script. They are critical, because they are the least practical ancient scripts with characteristics of both clerical scripts and ancient characters. The staging of bronze scripts is recommended for bronze scripts existed in a large time span including Shang, Western Zhou, Spring and Autumn and Warring States period. The bronze scripts of Western Zhou and Spring and Autumn are probably similar, but Shang bronze scripts and Warring States bronze scripts are differ widely. Moreover, Shang bronze scripts and bone oracle scripts are alike, and Warring States bronze scripts and Chu bamboo and silk scripts are alike. The categorizing of Shuowen scipts also important, and Simplified Characters and Shinjitai may use those variants like 礼 (ancient), 无 (Odd). I updated Chinese and Japanese Han etym template, and I hope they can be a reference to the future Han etym template. --Wargaz (talk) 09:30, 28 December 2017 (UTC)[reply]

By the way, I uploaded file:學-_oracle-v3 and file:學-_oracle-v4 with an extra space in the names, can you do me a favor and move them to proper names? Thanks. --Wargaz (talk) 09:46, 28 December 2017 (UTC)[reply]

Thanks! I'll try to incorporate the new file name system into English Wiktionary soon and deal with the Liushutong situation similar to what's done on the Chinese and Japanese Wiktionary. I can't move files, but I've requested a move to the correct names for those files. Justinrleung (talk) 09:55, 28 December 2017 (UTC)[reply]

NB : This conversation should eventually be moved to Commons talk:Ancient Chinese characters.

Hi everybody.

1/ I do know that "great seal" is a very disparate bag content, they obviously correspond to very different styles, but the main problems are "references" :

1. Given a "great seal" character (found in http://www.chineseetymology.org), where are the reliable sources for better classification of all those character forms? There was none when the project started, hence the choice.
2. Are there reliable references for such or such sub-category? Is the sub-category description sufficient so that any old character can indeed be found in that form, or is it just a sparse sample?

This being settled, which are the categories that are suggested for a better description of the "great seal" series (or for the "bronze" one)? and which are the time series that they represent?

2/ The main idea with these character series is not to be exhaustive but to present series that enable encyclopaedia readers to understand character evolution, because that is the only use so far. So the problem is not really to know whether such great seal character is of such or such kind, the only assumption is that the chronological evolution is "oracle > bronze > great seal > silk > small seal > present", which enables an automatic reconstruction of the evolution series with templates. The character representative of each series have been chosen so that the array do suggest how things have evolved, whatever the "real" period of each character.

This is how the classification has been used so far. Having different "great seal" (or bronze, or silk) character from different periods might confuse the scheme, which is not desirable : which character would be representative of an evolution? If because of a change the templates are unusable and the evolution has to be reconstructed by hand on every character, this is not an improvement... Will you volunteer to clean up the resulting mess?

If a proposed change results in a general disorganization of the present organization, with no realistic solution proposed, it cannot be allowed and must (and will) be vetoed.

3/ The point of a naming convention is to allow for automatic (template) processing ; if no such processing is needed the name is irrelevant. If the point is just to be specific as to which kind of style the character really is, a supplementary field may be added to the character description in the commons file to state its exact style and period - that is easy. Would that be enough?

What would be the usage of a different approach in the encyclopaedia or dictionaries? If there is another problematic that needs to be automatically processed in articles, alternative character series may be named using different sub-categories conventions, that would not interfere with the "character evolution" problematic. And in that case, having the same picture under two different names is not a problem.

But the point is, you can't expect the same naming convention to support two different problematic.

Michelet-密是力 (talk) 11:30, 28 December 2017 (UTC)[reply]

1/ My reference for such categories is The chapter of The Evolution of the Shapes and Styles of Chinese Characters in Chinese Writings by Chinese historian, palaeographer, and professor Xigui Qiu. (The English version was translated by Gilbert Louis Mattos and Jerry Norman.) In the book, he classified ancient scripts as Shang script, Western Zhou and Spring and Autumn script, six states script and Qin script. There are Chinese websites refer his classification like Chinese-linguipedia and Xiaoxuetang.

2/ The idea of presenting the character evolution is great, but the problem is the scripts from Liushutong is not belong to this chronological evolution. As I mentioned above, the historical chronological evolution would be "Shang script (bronze and oracle) > Western Zhou script (bronze and oracle) >Spring and Autumn script (bronze) > Warring States (bronze and silk for six states, bamboo and seal and slip for Qin) > (clerical script >standard script which are modern forms)'". In those brackets, the first ones are believed to be proper and formal form of their time, and the second ones are handwriting, vulgar and informal form. As you can see, scripts from Liushutong don't belong any stage of the chronological evolution, and the term great seal was invented by people of Han Dynasty. XIgui Qiu also suggested that "In order to avoid misunderstanding, it is best not to use this name." in Chinese Writing. Great seals for 學, 去, 用, 工, 世, 加, 軍, 先, 水, 合, etc. prove that neither scripts from Liushutong are prior to seal or they are proper or vulgar form of any given period of ancient scripts.

As I replied to Justinrleung, Xiaoxuetang and I consider that "transcribed ancient scripts" is a better name for scripts from Liushutong. I don't mean to say that Liushtong isn't important, and it just has a less priority.

As I implemented in Chinese and Japanese Wiktionary, -bronze are still the classical, typical Western Zhou bronze scripts, and every functions from old template are still present. It just have ability to detect -s, -sa, ,-w (Shang, Spring and Autumn and Warring States bronze), -slip (Qin bamboo and slip), -zhou, -ancient, -odd (Shouwen Zhou, ancient, and odd script). The CHinese Han etym template and English one operate in the same way when there are no additional svg files. Therefore, almost no additional work need to be done on previously files. I won't ask English Han etym template to change much, and it just need a few tweaks:

1. 1. Recognize files with -s, -sa, ,-w and automatically display them in Bronze inscriptions section;
   2. Recognize files with -zhou, -ancient, -odd and automatically display them in Small seal script section;
      1. Maybe rename that section to Shouwen script or just Shouwen;
   3. Recognize files with -slip and maybe replace great seal on main display area.
   4. Display -bigseal file along with other scripts from Liushutong in Large seal script section, and perhaps rename the section to transcribed ancient script or Liushutong.
   5. In the future, maybe set -shang and -oracle in the Shang script section and so on like the following example:

Without additional files, the template can work like before:

/3 Yes, of course it is enough. I just want some small tweaks on the template and never intent to cause any disorganization. With several tweaks the template can present a more historical and realistic chronological evolution. --Wargaz (talk) 00:52, 29 December 2017 (UTC)[reply]

OK :

• I understand that for practical purpose, http://xiaoxue.iis.sinica.edu.tw may be used as "the" reference for assigning detailed categories to Ancient Chinese Characters in the project. Is that correct? Is it always possible to refer to that database?
• The array is a good idea but is incomplete in its present state. What is the exact list of categories and sub-categories you intend to use, something like (1) name, (2) conventional suffixes for the ACC project, (3) classification according to xiaoxue ((甲)西周 = ???, and so forth), (4) chronological interval concerned, (5) kind of support (oracle / bronze / silk / bamboo / whatever) (6) cultural origin (Shang, Zhou, ...) (7) "default" classification for simplified templates.
• The templates used in .zh and .ja seem to work, but should be pretty-printed and translated avoiding Chinese characters in the variable names, for better readability (at least for me!).
• Since "bigseal" does not refer to any historical period, it should be altogether avoided in that template.

Michelet-密是力 (talk) 11:43, 31 December 2017 (UTC)[reply]

• It is possible to refer that database. Each character has its own number in the database. For example the number of 一 is 1. The oracle database is [1] , and the website use "?kaiOrder=" to call the character.

• If the files which uploaded before need more references, I will fix them. I can also try to add function to refer Xiaoxuetang to the ACClicense template. On Zhou oracle, you did have a point. Maybe -zy or -zhouyuan would be possible suffixes? Zhouyuan was the the historical site where Zhou oracle was found. The English Wikipedia doesn't have a page for Zhouyuan, so this is its Chinese Wikipedia page. In Dutch and Svenska WIkipedia, they use its Pinyin Zhouyuan as the title. Those oracles are often referred as Zhouyuan oracle in Chinese academia (周原甲骨, "Zhouyuan Shell-bone"). I believe as long as suffixes don't conflict with each other and can be distinguished, it is okay. Moving all -bronze or -oracle file also requires too much work, we can always use the old name which may not be accurate and give the file an accurate description in the template. (On dynasty name, I prefer to call it time period rather than cultural origin.)
• If you need a English version of Chinese or Japanese template, I will definitely translate for you. Maybe I will put it in my user page here. Those template were intended to be used by Chinese or Japanese native speakers, so I understand they are unreadable to you. My original thought was the English template can just have some tweaks and it doesn't need to be replaced.
• Although scripts from Lishutong isn't a part of character evolution, Lishutong is still kind of special. It collected every transcribed ancient scripts after Han dynasty. When ancient scripts are no longer official used, they are transcribed for two thousand years. In the process, some of them changed, and Liushutong recorded the changes. Liushutong would not be updated anymore, maybe wikifying it is still important (just not as important as unearthed ancient scripts). Therefore, maybe we can put them at the end of the template as the epilogue of ancient characters. --Wargaz (talk) 21:43, 31 December 2017 (UTC)[reply]

See also Template:Chinese characters naming.

Hello Wargaz. I'am doing light exploration to strengthen the Wikimedia's coverage for Kangxi radicals, frequent characters (?) and useful ones. Today I completed a bit the Template:Chinese_characters_naming with 中 in Kaishu, Xinshu (semi-cursive) and Songti. LiliCharlie uploaded the Kangxi (thanks to him!). The ACC project don't really focus on these post-Christ styles since fonts are generally available, but I think they are needed on Wikimedia for key characters and educational purposes (radicals at least). This is still exploratory and with very low coverage, so I added them in a section "New (2018)". Also, I noticed your effort on more subtle grouping for ACC. Also, feel free to complete this Template:Chinese_characters_naming with 中 images from your uploads. This page is one of our root documentation, so to include and visualize our subcategories and naming conventions to follow.

As for naming convention, previous naming conventions are based on principles :

1. contain an human friendly hint of the style (not the period)
2. for SO images and computing reasons :
   • the suffix-hint would be better to avoid {t|s|j|k|h} at its first letter. It's true for -order.gif, -red.png, -bw.png (black and white).
     • the -sbs.gif and -sbs.svg never took-off so we never picked a long term name.

Your work is adding information by precising the period of production. I'am not sure how to handle that. I would encourage you to use the Chinese_characters_naming page adding into it your -w.svg, -s.svg, and then consider an overall naming convention system more human-readable. It could be interesting to have some model such -{style}-{period}-{version}.svg, so images can be found by both style and period. As for the root images such as {zi}-oracle.svg, {zi}-bronze.svg, {zi}-bigseal.svg when many versions are actually available, our initial thought was to select the ones being the missing links between the picture and the traditional character, so it serves has elegant educational material (even if we are aware of the biases selection).

I come today with lot of feedback due to my recent discovery of your work and I may be out of touch for a big part, my sincere apologize if / where I do. Overall, thanks for your uploads. Yug (talk) 19:49, 11 January 2018 (UTC)[reply]

Thank you. Should we come up with better naming?

--Wargaz (talk) 01:03, 12 January 2018 (UTC)[reply]

By the way, it should be xíngshū or semi-cursive. I am afraid -xinshu isn't a good naming, either. I also suggest to rename -kaishu as -standard. In this glossary, Kaishu is translated as "standard script". It's just more fit in with clerical script, orcale script, seal script and so on. --Wargaz (talk) 01:12, 12 January 2018 (UTC)[reply]

Hello Wargaz, thanks for the pinyin correction, I didn't practice Chinese for few years.

Your 3 improvements sound good to me. It would be better to wait a bit for thinking, we then should be able to set up a sprint on those renaming . I'am in.

For Kaishu and Xingshu's coverage, they barely have files. The policy so far for those was "this is not the priority as fonts are available", so migration can be quite straight forward.

I for the question of name changes, I personally like the pinyin as it sounds more specific. « kaishu » sounds more meaningful (Chinese sounding, then when you know more "kai+style" or "Chinese standard style") compare to « standard » which don't carry any Chinese meaning. I also liked shorter names when possible. I here explain the former thinking, I also admit it's not consistent. I went to en:Chinese calligraphy but it was a mess as well (we actually are more consistent than them XD). I'am not fan of standard, too blur. Do we have alternatives.

For cao => cursive, let's go for it (if not yet).

For xing => semicursive, or an alternative. I want to avoid a 2nd « - » in the name, we use them as separator.

We can as of today add them on the summary table, to think about it in coming days and few weeks. This page needs further clean up on the ref section, namings (our talk), and maybe adding 1~2 colums and/or 1~2 category or page link by row. Yug (talk) 11:12, 12 January 2018 (UTC)[reply]

I'am not sure, because it date back to 2007 (!), but I think we got pinyin names for modern shapes (songti, kaishu, xingshu, caoshu), and basic-english ones for true ACC. I have a vague memory of that... Were we willing to signal a separation ? no idea. Yug (talk) 11:15, 12 January 2018 (UTC)[reply]

I am cool with semicursive and cursive . Certainly, most characters don't need a Kaishu ACC, and I think Songti are redundant, too. They can be input easily, and the defefault font for Unihan characters is Songti if I recall it correctly.

The text <span style="font-family:楷体;">我</span> will display the character 我 in Kaishu: 我 (Unfortunately, it doesn't support traditional Chinese, and I feel sad about it.)

Similarly, <span style="font-family:宋体;">我</span> will display the character in Songti : 我

I suggest that we can use this function, and no extra ACCs are needed. --Wargaz (talk) 11:34, 12 January 2018 (UTC)[reply]

I would like toconsistently cover the Kangxi radicals in these styles at least, for teaching purposes. Can be helpful for books and web{sites|pages|apps}, so they don't have to fight on both battlefronts (images and fonts). Some other meaningful characters as case studies as well. (PS: at work, can't edit further) Yug (talk) 13:06, 12 January 2018 (UTC)[reply]

Yug (talk) 10:04, 13 January 2018 (UTC)[reply]

Template:Chinese_characters_naming's table partially updated, so we visualize our current vision of names and improve it if needed.

Changes not implemented yet (no file moved).

A comment section.

It's 1am, continuing in next days. Yug (talk) 00:02, 14 January 2018 (UTC)[reply]

Hello there.

Thanks for your push on the table. I just added the File:中-caoshu.svg so the list is complete. It's quite impressive. I never realized we were covering that much.

I start to have a more global view. It indeed appears that MCC use pinyin while ACC use basic English. I have vague memories of a talk about it but can't recall on which page or which year.

I'am not pushing for name change as of now, need to cool down. Files renaming may also have negative impact on wiktionaries, I'am not sure the redirect will fill the gap.

Also, thinking via the {zi}-{style}-{period}.ext naming scheme :

• I noticed that we have "styles" which are generally defined by material tools and constraints in ACC. Then we have "periods" and/or "area" which thus carry some local (as in time and space) variation. Kangxi actually is a variant of Songti/Mingti, so -songti-kangxi.svg makes more sense if we want to be occurate and embed that fact into files' names.
• Last but not least, I'am starting to think that "bigseal" and "seal" actually are a same graphic style, the earlier being pre-imperial with multiple local variants, the later being imperial with Li Shi's standardization / unification. But both are the same style, same tools, same constraints. Thus, "bigseal.svg" would be better renamed "seal-preimperial.svg" and "seal.svg" either "seal.svg" or "seal-imperial.svg". But this would be a BIG BIG change in term of impact for the ACC project as 5000 files are in these chategories.

This is still exploratory, but it's clearly tickling me. Yug (talk) 10:02, 15 January 2018 (UTC)[reply]

It's also (unwillingly / unanticipated !) getting back in line with Chinese 6~7 traditional styles : Oracle, Bronze, Seal, Lishu, Kaishu, Xingshu, Caoshu.

We also have Bamboo and silk which are lesser know material supports and styles, but 9 with subsets on Commons VS 6~7 in traditional sources is cleaner than 17 on commons VS 6~7 in traditional sources. Yug (talk) 10:08, 15 January 2018 (UTC)[reply]

Ok, I made a rapid assessment of the most needed categories and datasets, via the first column of the template. Assessment for the SO and MCC categories is done. I made a draft assessment on the ACC categories, but I think you are more relevant than me for those, as I barely new of bamboo and silk scripts few weeks ago.

Also added quantification and links to associate categories. Links to tutorials are planed. We now have a comprehensive dashboard for the various projects. This now can be used as the basis for further internal discussion with active users.

When sorting and naming is solidified for ACC and MCC, I will move back to my own centers of interests . Yug (talk) 10:54, 16 January 2018 (UTC)[reply]

Thank you for you contribution! I have been busy about other things recently, so I didn't rely on time. Sorry about that. I also suggest we should consider about Zhouyuan oracle (as I mentioned above), the oracle bone scripts of West Zhou Dynasty found in Zhouyuan. I propose "-oracle-zhouyuan" as their name. --Wargaz (talk) 05:53, 17 January 2018 (UTC)[reply]

Hello Wargaz, you have an higher expertise for this period. If you think it fit, let's go for it, add it to the naming conventions page. Also, i shared the page and new naming scheme with LiliCharlie, so he can kind of review it and pinpoint short comings with fresh eyes. I worked so much on it that I don't really read its text anymore. Needs fresh eyes to push the last polishing. Yug (talk) 22:22, 17 January 2018 (UTC)[reply]

"I propose "-oracle-zhouyuan" as their name."

How do you handle variants of the same

甲骨文

character from

周原遗址

? Do you baptise such files "{Unihan Hanzi}-oracle-zhouyuan-1/2/3...", "{Unihan Hanzi}-oracle-zhouyuan-a/b/c...", or otherwise?

And how do you handle

甲骨文

characters from

周原遗址

that have no corresponding Unihan Hanzi? — Cf. Unicode's Roadmap to the TIP and note that what I call Unihan Hanzi here (e.g.

日、月、明

) are not Unicode characters for pre-Hàn Chinese characters, which will be encoded separately. —LiliCharlie (talk) 23:32, 17 January 2018 (UTC)[reply]

Zhouyuan oracle are just a few, and we just need to handle those cannot be found Shang oracle like "蜀". Unicode for ACC is a distant work in the future, and we don't have to use the corresponding character for each one. For example, as you say, the bronze, silk, and seal for "日" was fairly different from the MCC, for it was round like "☉". When ACCs are introduced to Unihan, it would have something similar to "☉". However, there are already variants in oracle and slip which are same as the modern "日" such as this one and this one. Even in bronze, you can find similar one like this one from late Shang and this one from mid Warring States. If we follow the rule that the name must correspond the form, it would create many file names which are not consistent and confusing. The ACCs I listed above prove that even in the system of ACC, square, rectangle and round are replaceable. "☉" and "日" are the same character, and a character can be less pictographic for writing or carving purpose. There are some very corresponding Unihan available now, but we didn't choose them as file names. For example, "𤰃" is the more corresponding one for ACC of "用", and "𠄞" and "𠄟" for "上" and "下". Beside the reason above, the more realistic reason for not choosing them as file name is file name on Commons don't support characters from Extension B, C, D, E, F. You can try to upload a file with tile that contains "𤰃", "𠄞" or "𠄟" via Upload Wizard, it will warn you that "Please choose a different, descriptive title (more info)." (and I cannot open the "more info" link). When Unihan supports ACC, I don't know it would take how long for wiki file titles to support them. I hope this could explain your questions. --Wargaz (talk) 05:29, 18 January 2018 (UTC)[reply]

Hello LiliCharlie, Hello Wargaz

For a little background explanation, the ACC project was initially designed as an effort to illustrate encyclopedic and language learning entries of current Chinese characters [in unicode] with a selection of their respective ancient styles. The tag phrase could be : « For each current [unicode] character and for each ancient style, one hand-selected svg illustration with predictable filename and format ». Going back in time and with the eyes of the initial ACC (2007!), the unicode 中 and Commons files 中-{style}.{ext} are not seen as referring to a graphic glyph, but rather seen as referring to the semantic concept of « middle », so both 中-shaped and non-中-shaped oracles glyphs documented as used with meaning en:in the middle of; zh-2018:中 by our sources could end up in the ACC project under 中-oracle.svg or 中-oracle-{idCode}.svg. As for death glyphs, we hadn't expected them to come up.

The ACC project was just not initially designed for the total complexity of countless variants in one given style (ex: Oracles for ), nor was it designed to handle dead signs or concepts. Handling this complexity is truly a new, 2017-2018 question. We had punctual cases before, but we really face this question since Wyangbot's mass upload, and since both Wargaz and yourself brought this expertise in. If by interest you decide to handle these cases as well, the naming conventions is either to use 中-{style}-{idCodeByYourSource}.svg or a new conventions of your creation. <Troll:> Will we come up with a DCC Dead Chinese Characters project ?</endTroll> Yug (talk) 13:31, 18 January 2018 (UTC)[reply]

Ok, should we move forward with "-oracle-zhouyuan" ?

Together with the understanding that ACC was initially designed for teaching purposes of nowadays unicode characters, so a system must be proposed for atypical cases as rightly exposed by LiliCharlie. Yug (talk) 11:41, 22 January 2018 (UTC)[reply]

Sure! I definitely agree. I will add -oracle-zhouyuan soon. --Wargaz (talk) 12:45, 22 January 2018 (UTC)[reply]

Please note that the root {character}-oracle.svg « bucket » should always be uploaded first, by a glyph being an elegant « missing link » between the current traditional character and the archaic image or realistic drawing. When more variations exist, the overflow then fill in the more specific namings such as {character}-oracle-{period}.svg. --Yug (talk) 14:33, 22 January 2018 (UTC)[reply]

Wikislow ! I'am entering a wikislow. I need to focus on other real life matters in coming weeks. But thanks for the collaboration, was very fun ! :D --Yug (talk) 16:04, 28 January 2018 (UTC)[reply]

It's okay. I understand. It was fun to me, too. :) I'm looking forward for next collaboration. --Wargaz (talk) 19:04, 28 January 2018 (UTC)[reply]

It seems there are light differences between mingti and songti. I added a source about it :

• Fundamentals of Chinese Typography: #1 Fonts Styles (Songti, Fangsongti, Mingti, Heiti, Kaiti)

Will update naming convention accordingly. --Yug (talk) 09:20, 13 March 2018 (UTC)[reply]

Done.

We start to have something* pretty net I think. (* = the naming conventions)

I added them to the project home page.

May deserve JS accordion, to hide by default, and display if needed. Not sure, bottom of page is already hiding it a bit.

My global objective is to provide a super net place so new comers, with coding skills or graphic skills, can take over one axe and attack quite quickly, with right info on home page.

Seems we are on good way. Yug (talk) 09:53, 13 March 2018 (UTC)[reply]

The Songti, Mingti, Songti-kangxi deserves more attention. I'am not sure Songti-kangxi is song anymore. And maybe we should just get one. Yug (talk) 09:56, 13 March 2018 (UTC)[reply]

Also may lower them 3 to one dot. Yug (talk) 10:24, 13 March 2018 (UTC)[reply]

This message was added automatically by MifterBot ^{(Talk • Contribs • Owner)}, if you need some help about it please read the text above again and follow the links in it, if you still need help ask at the → Commons:Help desk in any language you like to use. --MifterBot ^{(Talk • Contribs • Owner)} 09:33, 24 January 2018 (UTC)[reply]

Hello, Wargaz. I see you recently made edits to Template:ACClicense that resulted in changing the categorization of some files. In particular, two files (that haven't recently been edited) now appear in Category:橋. That category is a redirect to Category:Bridges, but the two images that are now populating that category do not appear to have anything to do with bridges. I do not read Chinese, so I have no idea whether it is the redirect that is wrong, or the categorization of the two files. However, it seems likely that one of them must be wrong. Perhaps you can help clear up the mystery. --R'n'B (talk) 16:49, 1 February 2018 (UTC)[reply]

Hello, R'n'B. I edited {{ACClicense}} recently, but it might not be the result of my editing. That is the way how the {{ACClicense}} works originally: it categorized a character's ACCs into its category. 橋 is the Chinese character for bridges, so it's a wrong redirect. Category:橋 should have its own page to contain ACCs and MCC of 橋. Thank you for reminding me, and I will fix this. --Wargaz (talk) 23:17, 1 February 2018 (UTC)[reply]

@R'n'B: , the redirect was wrong. A category for photographs of bridges should always have an English name, due to conventions in Commons. All categories named with a single Chinese character contain images of that character - and nothing else. -- sarang♥사랑 22:03, 2 August 2018 (UTC)[reply]

Hello Wargaz,

I'am interested to slowly push forward the ACC coverage for the list of characters in Commons:Ancient Chinese characters project/Priority. This list who come from the Chinese MOOC in French. I lost track of the ACC sources to use... I currently plan to use ChineseEtymology but maybe you can advice me on the best source to use as of 2018, or the specifics --strengths and weakness-- of each sources. Any thing I most know before to go forward ? Yug (talk) 21:04, 8 February 2018 (UTC)[reply]

Hi Yug, I'm glad that you got some free time. Good news! I just finished the renaming of the old convention. I suggest that you can try to use Sinica Database and Multi-function Chinese Character Database.

With Sinica Database, you can easily get 300px image or any other sizes. The UI is all Chinese, but you may use built-in translators which are available in many browsers. Sinica Database is funded by National Science Council of ROC Executive Yuan and developed by Department of Chinese Literature of National Taiwan University, Historical Language Institute of Academia Sinica and Institute of Information Science (About Sinica Database) It is more reliable than ChineseEtymology. The UI of Multi-function Chinese Character Database supports English, so it is much user-friendly to non-Chinese speakers. The drawback is their images is too small.

On ChineseEtymology, I thank Richard's work, but information on his website is really outdated. He uploaded decade-old versions of Collection of Oracle scripts and Bronze inscriptions many years ago, and many are still old Interpretations like oracle for 春 and 秋 in ChineseEtymology. The so-called "great seals" in your template, characters from Lishutong is not a process of character evolution and don't have teaching, historical and academic value. The real process in there is Warring States scripts which are mainly represented by Bronze, Chu Bamboo and Silk and Qin Bamboo and Slip in our project. Warring States scripts is the one of hottest topic in Chinese grammatology, and they are not represented on ChineseEtymology at all. Furthermore, most source of Chu Bamboo and Silk as well as Qin Bamboo and Slip are introduced and informative on English Wikipedia (all of Qin bamboo and slip of Sinica Database are from Shuihudi Qin bamboo texts, the Chu bamboo and silk are from Guodian Chu Slips, Shanghai Museum bamboo slips, Baoshan bamboo slips and etc. Those information can be viewed on the 出處表 source table of Sinica Qin script database and Chu script database), but the book Liushutong which is the source of most "great seals" of our project doesn't have a page on any version of Wikipedia, even the Chinese one. In contrast, Shouwen Jiezi is much more well-known than it, as well as on importance.

--Wargaz (talk) 01:35, 9 February 2018 (UTC)[reply]

Hi, thanks a lot for the sum up.

(1) The background solidity of Sinica is awesome. 2018 is great .

(2) I'am discovering the depreciated value of greatseal = bigseal (=LST if i remember well). It's unfortunate.

*-bigseal.svg (1,835 files) was one of the core styles and steps on the ACC's [artificial] evolutionary path for Chinese characters.

If bigseal is not relevant, I'am still confuse about what to do with it. Should we drop this bigseal style from the core ACC's evolutionary path / priorities ? Should we rather replace it and put focus on the -bronze-warring.svg ?

(3) We likely should create an entry for the Liushitong, even supershort as long as we have one source, but so we know and agree at less a bit what we are talking about here on the ACC.

PS: I will come back and reread your message to process it better. Yug (talk) 15:05, 10 February 2018 (UTC)[reply]

Ok, according to Template:Chinese characters naming (ps: I love this page!), it seems we are phasing out focus on bigseal : only 1 dot in the priority column. Good to know !

Also, thanks for the files' migration. Yug (talk) 19:37, 10 February 2018 (UTC)[reply]

Thanks for listening! I used to share my view on big seal with Micheletb, but it seems like he showed less interest. I know that maybe he left ACC project for a while. Sure, we should more focus on -bronze-warring,svg, as well as -slip.svg and -silk.svg, they are putty much reflect the diversity of Warring States script by geography and time. --Wargaz (talk) 19:53, 10 February 2018 (UTC)[reply]

do you have any more files to add or process in batches? I'll help. Artix Kreiger (talk) 02:47, 14 February 2018 (UTC)[reply]

Certainly! Thank you for helping me!

• File:巴-bronze.svg
• File:匋-oracle.svg
• File:前-oracle.svg
• File:乖-bronze.svg

The files above should be deleted, and I wait for a long time. --Wargaz (talk) 02:50, 14 February 2018 (UTC)[reply]

In addition:

• File:包-bronze.svg
• File:全-bronze.svg

Thanks again! --Wargaz (talk) 02:55, 14 February 2018 (UTC)[reply]

File:Rubbing of the Inscription Ding of Dayu Tripod.jpg is precise and Copyright Free. I hope that more scholars and students use this image. --ReijiYamashina777 (talk) 01:14, 14 April 2018 (UTC)[reply]

Oh, actually, all of images under Category:Rubbings of inscriptions on Chinese bronzes, because they are over 50 (~100) years old. I just edited File:Da Yu ding inscription.jpg. The characters on File:Da Yu ding inscription.jpg are clearer and more precise to me, and the image has higher contrast and resolution. What's wrong with that one? --Wargaz (talk) 01:27, 14 April 2018 (UTC)[reply]

File

Rubbing of the Inscription Ding of Dayu Tripod.jpg is from the Shanghai Museum 1959 book. It may be more precise than File:Da Yu ding inscription.jpg from the Kao Ming book. I hope the more precise image be popular and you use that.--ReijiYamashina777 (talk) 01:35, 14 April 2018 (UTC)[reply]

Okay. You are right about it. --Wargaz (talk) 04:24, 14 April 2018 (UTC)[reply]

Hi. When a file has been at a location for a long period, and then moved, we would usually keep that redirect. If someone has linked to the file externally, we don't want to break that link, remembering that Wikimedia allows external pulls of our images.  — billinghurst sDrewth 13:29, 21 April 2018 (UTC)[reply]

@Billinghurst: I want to break that link, because its external pulls. All of "-bronze" in ancient character project are Western Zhou (1046–771 BC) bronze inscription characters, and all of "-bronze-warring" are Warring States (476 to 221 BC) bronze inscription characters. If you insist to keep the redirects, it would display this in all Wiktionaries:

Warring States (戰國)	Shuowen (說文, 漢)
Bronze inscriptions	(小篆) Small seal

and I have to add "bronze=N/A" in the Wiktionaries in order to display like this:

{{:User:Wargaz|冰}}

Warring States (戰國)	Shuowen (說文, 漢)
Bronze inscriptions	(小篆) Small seal

However, since English and French Wiktionaries' {{Han etyl}} don't support this function, they will display the wrong images. If you allow me to fix them, that won't happen. --Wargaz (talk) 15:33, 21 April 2018 (UTC)[reply]

I am not saying not to move the files, I am saying that we leave the redirects. If you have files that are being pulled after that by templates, then please fix the templates. If you have files that are being pulled by Wikidata links, then these should be resolved by the moves, though you should double check that they do update.  — billinghurst sDrewth 15:36, 21 April 2018 (UTC)[reply]

Please fix the templates at the wikis.  — billinghurst sDrewth 15:48, 21 April 2018 (UTC)[reply]

@Billinghurst: No. English and French WIktionaries' {{Han etyl}} cannot be fixed in this way. --Wargaz (talk) 16:17, 21 April 2018 (UTC)[reply]

I find "can't" hard to believe, in my extensive experience with wikis and templates, however, if that is the case then replicate the alternate templates. This issue should be resolvable without having to delete the redirects.  — billinghurst sDrewth 16:32, 21 April 2018 (UTC)[reply]

@Billinghurst: English {{Han etyl}} has some functions which the alternate template doesn't have, and I don't know how to merge them. I don't speak French, and I honestly don't know how to modifier the French template. If you could, please help me to solve those problems. --Wargaz (talk) 17:44, 21 April 2018 (UTC)[reply]

Nope. It is not Commons job to solve Wiktionary issues. Find those skills, or ask your questions at the appropriate forums. As been said, removal of redirects breaks any existing external linking to files, and that is not done casually, and not be speedy deletion.  — billinghurst sDrewth 02:30, 25 April 2018 (UTC)[reply]

As an administrator of this site I have explained to you what exists for the rules at Commons. Please stop nominating this file for deletion. My other options are to protect the file, or to block you, neither of which are worthwhile. Your sites' templates are the problem here, not the files, or the names, fix them!  — billinghurst sDrewth 03:07, 25 April 2018 (UTC)[reply]

@Billinghurst: The names are problems. In the Ancient script project of the Commons, -bronze files are for Western Zhou bronze images, and -bronze-warring are for Warring States bronze images. Please read this and this. 冰 do not have Western Zhou bronze but only Warring States bronze, so it should not have a -bronze redirect. I thought that I explain enough of this to you, but you still do not understand. I don't why. --Wargaz (talk) 03:17, 25 April 2018 (UTC)[reply]

You have explained that, and I have explained that, and that is why the rename was undertaken. Fix your templates, or directly link. I have explained why we keep redirects for long existing files.  — billinghurst sDrewth 03:22, 25 April 2018 (UTC)[reply]

@Billinghurst: They cannot be fixed. They are not even my templates. I didn't create them, and I don't know how to modifier them. You just don't let wrongly named redirects go. Other users upload wrongly named files and created English and French templates, and you let me to fix everything that caused by their problems. --Wargaz (talk) 03:50, 25 April 2018 (UTC)[reply]

Do not come and start blaming me for the issues that you face. I didn't request the files to be moved. I didn't write the templates. I denied your deletion request as it is outside the existing policy to speedy delete a file redirect, especially where the file has an extended history. If you wish to suggest a change to the policy/guideline, then you go for it.

The problem does NOT lie with the filename, the problem lies with the template at whichever wikis that the problem exists. If you cannot fix the templates, then get the communities to fix them, it is their responsibility. It is simply untrue to say that the templates cannot be fixed.

It is truly unfortunate that there are issues, however, your simple solution to delete redirects causes other general issues for anyone externally linking to a file, and that is also bad. Your presented case does not meet the standard for me to step outside of the guidance, as there are alternate solutions.  — billinghurst sDrewth 12:23, 26 April 2018 (UTC)[reply]

Hey, is this issue solve ? Yug (talk) 17:31, 15 September 2020 (UTC)[reply]

Hi. I don't think it's a good idea to redirect to these files, like File:亟-bronze-spring-2.svg to File:ACC-b18639.svg. Wouldn't it be better to move the ACC- names to something more meaningful? Also, if we do use redirect detection as a way to go around the bad redirect issue, then these redirects would not work. Justinrleung (talk) 03:38, 26 April 2018 (UTC)[reply]

Oh, I thought about that before, but waiting for administrators to move is really waste of time. I think that we only need to delete bad redirects and keep the good ones. After all, if we do move File:ACC-b18639.svg to File:亟-bronze-spring-2.svg, a File:ACC-b18639.svg redirect is still needed for the Han Etym template on English Wiktionary. --Wargaz (talk) 04:23, 26 April 2018 (UTC)[reply]

No, the File:ACC-b18639.svg redirect would not be needed because it's not part of the template that relies on the naming convention. We just need to change the data modules for the dropdown part. Justinrleung (talk) 04:27, 26 April 2018 (UTC)[reply]

Okay, that's a good idea, but the major problem is that means we need to rename thousands of files if we do so... There are at least two thousand bronze files with ACC- names and two thousand oracle files with ACC- names. Besides, I do know how to achieve this on English Han Etym template yet. --Wargaz (talk) 05:55, 26 April 2018 (UTC)[reply]

We don't have to rename all of them, just the ones that you think are suitable as the ones that display without clicking the dropdown. Justinrleung (talk) 06:08, 26 April 2018 (UTC)[reply]

Then the amount of work will be reasonable. However, if we delete the redirects after we renamed those files, red links will appear in the hidden area just like this one. Do we just delete them in the glyph-data? --Wargaz (talk) 06:26, 26 April 2018 (UTC)[reply]

I'm not sure why you would delete these kinds of redirects since they're useful, but they do get deleted, we can change the glyph data to have the right file name or remove the name from the glyph data. Justinrleung (talk) 06:44, 26 April 2018 (UTC)[reply]

Oh, sorry. I misunderstood something. I would definitely keep if I could, and I will follow this as my new guideline in the future. However, how to delete those bad redirects like File:冰-bronze.svg and File:覺-silk.svg? The enthusiastic administrator just won't let me do anything about that. --Wargaz (talk) 06:58, 26 April 2018 (UTC)[reply]

FYI, this "enthusiastic" administrator is an experienced administrator of long-standing (and not solely at this wiki) who was elected by the community to uphold the policies as determined by the community. The purpose of the policies and guidelines is to attempt generate a consistent approach, not to react to demands of individuals who think of solutions for their limited subset of problems and may not be paying sufficient attention to issues that they may cause. If you don't like the policies/guidance as they are currently prescribed, then seek a new consensus for a change, and that will be the paradigm to which I will administer, until then ...  — billinghurst sDrewth 12:36, 26 April 2018 (UTC)[reply]

I feel speechless. I told before that redirects like FIle:冰-bronze.svg are incorrect according to Ancient Chinese characters project naming rules, and no one should refer File:冰-bronze-warring.svg as File:冰-bronze.svg. Currently, only our Han etym templates use those files, and we ARE fixing the links. In the future, if ANYONE who wants to refer File:冰-bronze-warring.svg, they should NOT refer it as File:冰-bronze.svg. Because according to ACC naming rules that is an incorrect named redirect. --Wargaz (talk) 17:10, 26 April 2018 (UTC)[reply]

I don't think we can do anything about these bad redirects under the current policy. What we have to do is find another way to deal with this from the Wiktionary side of things, which is what I'm trying to do on English Wiktionary. Justinrleung (talk) 18:11, 26 April 2018 (UTC)[reply]

Thanks for your effort, Justinrleung. --Wargaz (talk) 18:34, 26 April 2018 (UTC)[reply]

Hi Wargaz, you do a great lot of maintaining Chinese characters, thank you. This work causes many categorizations; some need to be defined.

As an example: File:夸-oracle.svg becomes categorized to Category:夸, which is not yet existing. This category is easy to provide, with the template CJK category; it needs the parameters (you can get all of them from en:wiktionary, in this case from 夸)

1. radical number, in this case "037"
2. additional strokes, in this case "3"
3. the Unicode codepoint, in this case "U+5938"

So with {{CJK category|37|3|U+5838}} the category for "夸" will be defined. I wish you further good success! -- sarang♥사랑 22:03, 2 August 2018 (UTC)[reply]

I collected this failing categories into the (not existing) Category:Commons:Maint:ACClicense, currently it contains 4,649 files, so some hundred categories need to be defined as told above. I can define 3 to 4 such cats within one minute, so it seems a work of two to four hours. A bot could do it faster, but I have none and have no access to any. So it might be the best if we two start with this work, slowly, reducing the missing categories one by one. -- sarang♥사랑 04:44, 6 August 2018 (UTC)[reply]

Differentiation: when there is only one occurence in the wanted category, it seems better not to create the category for that but to categorize it with Rcat. This can be done adding to the template ACClicense the parameters 6=<radical number> as above and strokes=<strokes> as above, plus the additional parameter cat=r. Example: 鴜-seal.svg.

When later the category would be defined, Rcat will categorize automatically to that category.

In any case (CJK category, or Rcat) an unspecified {{inkscape}} should be removed, and the AClicense-parameter i=i should be set instead. -- sarang♥사랑 11:59, 8 August 2018 (UTC)[reply]

Thank you for all your categorizing work! To your information: After several changes of Template:ACClicense, it can now hopefully recognize which is the correct category in Valid SVG created with Inkscape:Chinese scripts or Valid SVG created with Potrace:Chinese scripts. So it seems not anymore needed to specify the subcategory and topic with e.g. s=sh or s=wz. On the contrary, I want to get rid of these deprecated topic specifications, since all can be done with ACClicense much better (in case it should not be possible to use ACClicense, another solution like at Character Eye Oracle.svg is as well possible). So I will remove in new future the topics lst sa sh sw ws wz, and I am removing it from the file descriptions with ACClicense.
Because the drawings are showing Chinese characters and not glyphs, I changed as well the name of the main categories (which can serve as default categories, if needed) to "Chinese scripts". If you want any information or explanation, just ask! -- sarang♥사랑 07:14, 1 September 2018 (UTC)[reply]

Thank you for your work and informing me! I will notice those chances in the future. --Wargaz (talk) 16:27, 2 September 2018 (UTC)[reply]

Deutsch ∙ English ∙ español ∙ français ∙ italiano ∙ magyar ∙ Nederlands ∙ português ∙ sicilianu ∙ slovenščina ∙ svenska ∙ Tagalog ∙ Tiếng Việt ∙ Türkçe ∙ македонски ∙ русский ∙ मराठी ∙ বাংলা ∙ മലയാളം ∙ 日本語 ∙ 中文（简体） ∙ 中文（繁體） ∙ العربية ∙ +/−

Hello. This message is being sent to inform you that there is currently a discussion at Commons:Administrators'_noticeboard/User_problems#User:Wargaz and User:Micheletb. This is in relation to an issue with which you may have been involved.

BTW are you aware of Commons:Overwriting existing files? Incnis Mrsi (talk) 13:54, 5 December 2018 (UTC)[reply]

Hello! As the producer of File:Universal Declaration of Human Rights Zhuang Sawndip-Unicode 10.png I can assure you that this was not designed as a replacement for File:Universal Declaration of Human Rights Zhuang Sawndip.png. The earlier file is in simplified characters whereas the newer file uses traditional characters, and as such are very different. The newer file was created specifically for https://en.wikipedia.org/wiki/Help:Multilingual_support_(East_Asian) to allow people to test font support for Sawndip characters in Unicode 10. Johnkn63 (talk) 12:58, 8 January 2019 (UTC)[reply]

Hi Wargaz, I am glad that you are also categorizing the AC, and that you can understand & use the necessary parameters and templates. There is a lot to do! One issue can be discussed: When there are too many characters ruled by a radical, of course it will give a page somehow overloaded. An image can be seen immediately when it is not subcategorized; on the other hand, too many occurencies of the same character in the category of the "ruling" radical might be not so good for a swift look; the same problem cones from too many subcategories.
Te me seemded a good compromise not to create a subcategory when there is only one image for an AC, like 陵. I would not do it even when there are two images. I subcategorize (CJK category) just for three and more ancient character images; less images become CJK-singles - until the category becomes created.
Of course, everybody can handle this issue as he likes. Nevertheless I want to tell you how I see it, so you can decide. Good further success! -- sarang♥사랑 14:10, 13 April 2019 (UTC)[reply]

Thanks for the explanation on your last rename request, though I have declined it. Please take the list of renames that you are desiring to have undertaken to Com:Village pump and put to the community. If I understand your last request, after the move, you would be reassigning the redirect to another image. Reassigning redirects is not something that we would generally do for a file that has existed for a while, as anyone using that link externally would then get a different file. Such a move or series of moves should have an open discussion, and the consensus of the community, not the decision of one. Thanks for your understanding on this.  — billinghurst sDrewth 11:54, 8 June 2019 (UTC)[reply]

It would also be useful for you to better familiarise yourself with Com:Rename as there are specific requirements that administrators need to consider. Retention of redirects is quite particular here.  — billinghurst sDrewth 12:24, 8 June 2019 (UTC)[reply]

As said previously, speedy is not the way to handle this. Your wiktionary templates do not override Commons rules for long existing files, and how redirects should remain.  — billinghurst sDrewth 12:56, 17 June 2019 (UTC)[reply]

RMaung (WMF) 01:14, 10 September 2019 (UTC)[reply]

你好，Commons:Deletion requests/File:旳-seal.svg討論結束了，不曉得你是否知悉，有沒有意見？--Roy17 (talk) 13:44, 20 September 2019 (UTC)[reply]

沒甚麼意見。是不可能旳。生气。很簡單旳事就是跟他們說不明白，死腦筋，如果in use刪點再重定嚮到旳-seal.svg影向甚麼了麼？規則是死旳人是活旳，在這裏真旳看不出這點。鬧心。--Wargaz (talk) 21:40, 20 September 2019 (UTC)[reply]

可是把「明」字上載到 File:的-seal.svg 然後要求更名做 File:明-ancient.svg 就很有問題喔。 Justinrleung (talk) 22:33, 20 September 2019 (UTC)[reply]

依然是用我方式維護古文字計畫。事實上就是正常旳訴求不能滿足，止能多迻花接木。估計照樣失敗，反正對貴站很失朢，沒有貢獻欲朢。貴站愛圈地自萌就繼續罷。--Wargaz (talk) 00:39, 21 September 2019 (UTC)[reply]

那個結束討論的管理員應該不懂中文也不懂咱說的啥，純粹是以文件正在使用為由保留。我明白你的提刪依據。我的提議，將所有正在使用 的-seal.svg 的頁面換成 旳-seal.svg 或者直接去掉，你覺得如何？如果你同意、維基辭典的用戶沒有異議，不妨重新提出刪除文件。--Roy17 (talk) 21:34, 21 September 2019 (UTC)[reply]

我明白了，File:的-seal.svg是Justinrleung上傳旳，所以即使這文件旳質量很差，他也要維護（我雖不會這樣但我理解他旳心理），那我就提刪我自己旳文件好了，盡量把鏈接弄掉，刪自己旳文件旳請求好過一些，再重命名文件和以質量好旳版本覆蓋當前質量差旳，我妥協，這樣也不違反社羣規則，額能尊重Justinrleung不刪他旳文件，但願這樣他能滿意。--Wargaz (talk) 21:45, 21 September 2019 (UTC)[reply]

不需要哦。現在其實 的-seal.svg 根本是一個重複文件（和 旳-seal 事實上是一樣的），而且存在是沒什麼意義的，完全可以提刪，只不過那個管理員糊塗罷了。--Roy17 (talk) 21:53, 21 September 2019 (UTC)[reply]

如何能知道下次處理提刪旳管理員不糊塗？這裏旳管理員攪混水我都看得夠了，因爲看不懂漢字就認爲二者不是重複文件旳情況我也受夠了，我看還是把握旳方式比較好，畢竞是我當時糊塗了沒有注意到先有File:的-seal.svg，是FIle:的-seal.svg先有旳再有我旳重複文件，當時我如果沒不確認下就上傳也不會有這麼多幺蛾子，我旳過。--Wargaz (talk) 22:01, 21 September 2019 (UTC)[reply]

(edit conflict) 我不是要特別維護我上傳的文件，只是如果只有 File:旳-seal.svg 這個文件，那麼所有的維基辭典都不能使用現行的模板把「的（旳）」的小篆顯示在「的」的條目。維基辭典大致上遵從 descriptivism，因為「的」比「旳」常用，就會以「的」為主要條目，因此字源也得放在「的」較為方便。要嘛我們說 File:的-seal.svg 是 File:旳-seal.svg 的 duplicate，將 File:旳-seal.svg redirect 到 File:的-seal.svgFile:的-seal.svg redirect 到 File:旳-seal.svg。 Justinrleung (talk) 22:07, 21 September 2019 (UTC)[reply]

所以說不知道可以用重定嚮？而且請勿說所有旳字源模板，我編輯過我知道，止有英文和法語旳字源模板比較蠢，不能在頁面下顯示不同名旳字旳圖片，中文和日文詞典旳字源模板是能作到旳，另外中文和日文旳字源模板也是我改良旳，後面伱描述旳問題，依然可以用重定嚮解決。我仍不知伱在糾結甚麼。--Wargaz (talk) 22:24, 21 September 2019 (UTC)[reply]

而且伱提descriptivism我更不理解了，描述主義是不是要描述事實？那个小篆也是「旳」而不是「的」，按描述主義描述事實那文件名是不是應是「旳」而非「的」？很明顯在文件名上閣下就爲了「方便」放弃descriptivism了呀?--Wargaz (talk) 22:29, 21 September 2019 (UTC)[reply]

回Wargaz： 的-seal是2017，旳-seal是2015呢。旳-seal早一些。管理員就不要管他啦。假如各位維基辭典編輯協商好了，請一個中文管理員幫忙也可以嘛。

@Justinrleung: 可是事實上是錯的哦。日勺是旳怎麼也不是的，純粹是後世人把旳寫成的，不能說日勺是的的篆體吧。

我想問兩位，其它這樣的字，維基辭典是怎麼處理的？還有甲骨文是怎麼處理的？（甲骨文的字比篆體更少，有現代字沒甲骨文的現象應該更多吧。）--Roy17 (talk) 22:27, 21 September 2019 (UTC)[reply]

（edit conflict）（我上面有誤，應該是File:的-seal.svg redirect 到 File:旳-seal.svg。）我們通常都是以現今通行的寫法作為檔案名稱。結構上絕對是「旳」比較正確，可是「的」是從「旳」衍生的訛化字，而且是現今通行的寫法，所以也是個合理的檔案名稱，作 redirect 應該是說得通的。對，描述主義是要描述顯示，所以我們以「的」為主要條目，為了方便解釋字源的關係，File:的-seal.svg檔案應該要保留。（為什麼你要把我們的字都改成古文？改得「旳」「的」都分不清。） Justinrleung (talk) 22:46, 21 September 2019 (UTC)[reply]

瀏覽器自動轉換，沒有鉤選轉換文本框，卻有時仍能轉換維基文本框，鬼知道怎麽回事。請問File:的-seal.svg重定嚮到File:旳-seal.svg影向了伱說旳「方便解釋字源」了麼？是否爲了通行旳寫法依然可以犧牲descriptivism？因爲該圖不是「的」而是「旳」，伱把文件名定爲「的」就沒有正確描述該圖。何況「旳」是Unicode基本區，可以方便旳輸出，也不是Extension B+字不能作爲文件名。--Wargaz (talk) 22:54, 21 September 2019 (UTC)[reply]

「旳」和「的」是異體字關係，所以把「的-seal.svg」重定向到「旳-seal.svg」應該沒問題。因為英文維基辭典「的」詞目裏的字源模板暫時只能取得「的」開頭的檔案，所以重定向會有幫助。命名的問題很複雜，因為涉及技術問題，所以重定向是權宜之計，這並不是犧牲描述主義。圖裡的字其實既不是「的」，又不是「旳」，而是小篆。篆書楷化確實是「旳」，可是「的」也是「旳」現今的一種寫法，所以不算是描述錯誤。 Justinrleung (talk) 23:12, 21 September 2019 (UTC)[reply]

伱這段話我更看不懂了，「既不是『的』，又不是『旳』，而是小篆」：它是「旳」小篆，「旳」小篆不是「旳」？伱在混淆書體和漢字，但這不是伱旳錯而是中國兩岸三地漢字敎育都忽略而已。「的」楷書也和這印刷體「旳」不完全一樣，難道伱要說「既不是『的』，又不是『旳』，而是楷書」？

首先我們研究漢字的，必須弄淸楚兩个概念——書體和漢字。

前者（書體）是書法裏頭的概念，是指同一个漢字由不同的手書所形成的書寫風格。 後者（漢字）是文字學概念，是指有其獨立的字音、字形（主要看構字部件及其佈局）、字義的文字，竝且區別於其他字。

簡單來說，漢字是一个抽象的稱謂，表達的是由構字部件組成的含有獨立音形義的文字；而書體則是漢字字形的具體表現形式，同一个漢字可以寫成不同的書體，但是仍然認定爲同一个字（在文字學意義上）。

https://pic2.zhimg.com/80/891d11294494fc40c80097c972bede06_hd.jpg （引用自简化字 - 汉字 - 知乎专栏）

如上圖所示，這裏所列出來的都是「請」字的不同書體，但是表示的都是「請」這个字。 @波斯基曰： 我们甚至可以认为「說」、「説」、「说」是同一个字的不同书体写法，是同一个字的三种不同书写风格，是同一个字的三种不同字形风格；但从字形、字构的角度看，这就是同一个字。 其說甚是。

做一个簡單的類比： 漢字 水（抽象的物質概念）

書體 水（具體存在形式，如水蒸汽、液態水、冰等）

— 趙瑾昀, in: https://www.zhihu.com/question/23752384/answer/25549761

--Wargaz (talk) 00:48, 22 September 2019 (UTC)[reply]

兩位認同的話，就提出刪掉 的-seal，重定向到 旳-seal，好嗎？--Roy17 (talk) 23:50, 21 September 2019 (UTC)[reply]

@Roy17: 我沒有異議。Wargaz兄，我也同意上述的大部分。如果我瞭解沒有錯誤，至少我們應該可以同意「的」、「旳」跟上述的「說」、「説」、「说」一樣，大概都可以當作是「一個字的不同書體寫法」吧。 Justinrleung (talk) 03:57, 22 September 2019 (UTC)[reply]

RMaung (WMF) 15:24, 20 September 2019 (UTC)[reply]

RMaung (WMF) 20:04, 3 October 2019 (UTC)[reply]

Hello,

Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at Wikimedia Commons.

I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!

From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.

If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.

Thank you!

--User:Martin Urbanec (talk) 22:04, 23 November 2019 (UTC)[reply]

This message was added automatically by MifterBot ^{(Talk • Contribs • Owner)}, if you need some help about it, please read the text above again and follow the links in it, if you still need help ask at the ->Commons:Help desk in any language you like to use. --MifterBot ^{(Talk • Contribs • Owner)} 03:02, 6 June 2020 (UTC)[reply]

العربية ∙ беларуская ∙ беларуская (тарашкевіца) ∙ ပအိုဝ်ႏဘာႏသာႏ ∙ বাংলা ∙ català ∙ čeština ∙ dansk ∙ Deutsch ∙ Deutsch (Sie-Form) ∙ Ελληνικά ∙ English ∙ español ∙ euskara ∙ فارسی ∙ suomi ∙ français ∙ galego ∙ עברית ∙ hrvatski ∙ magyar ∙ հայերեն ∙ italiano ∙ 日本語 ∙ ಕನ್ನಡ ∙ 한국어 ∙ lietuvių ∙ latviešu ∙ македонски ∙ മലയാളം ∙ मराठी ∙ မြန်မာဘာသာ ∙ norsk bokmål ∙ Plattdüütsch ∙ Nederlands ∙ norsk ∙ polski ∙ português ∙ română ∙ русский ∙ sicilianu ∙ slovenčina ∙ slovenščina ∙ српски / srpski ∙ svenska ∙ ไทย ∙ Türkçe ∙ українська ∙ اردو ∙ Tiếng Việt ∙ 中文（简体） ∙ 中文（繁體） ∙ +/−

This media was probably deleted.

Thanks for uploading File:請 written form differences.jpg. This media is missing permission information. A source is given, but there is no proof that the author or copyright holder agreed to license the file under the given license. Please provide a link to an appropriate webpage with license information, or ask the author or copyright holder to send an email with copy of a written permission to VRT (permissions-commons@wikimedia.org). You may still be required to go through this procedure even if you are the author yourself; please see Commons:But it's my own work! for more details. After you emailed permission, you may replace the {{No permission since}} tag with {{subst:PP}} on file description page. Alternatively, you may click on "Challenge speedy deletion" below the tag if you wish to provide an argument why evidence of permission is not necessary in this case. Please see this page for more information on how to confirm permission, or if you would like to understand why we ask for permission when uploading work that is not your own, or work which has been previously published (regardless of whether it is your own). The file probably has been deleted. If you sent a permission, try to send it again after 14 days. Do not re-upload. When the VRT-member processes your mail, the file can be undeleted. Additionally you can request undeletion here, providing a link to the File-page on Commons where it was uploaded ([[:File:請 written form differences.jpg]]) and the above demanded information in your request.

 

shizhao (talk) 02:38, 28 August 2020 (UTC)[reply]

Hello Wargaz, I may need your help on this one. We have two new categories :

• Category:Clerical Han script characters
• Category:Clerical Qing script characters

I filled the ACC template such as {ACClicense|禾|clerical-han|....} and {ACClicense|禾|clerical-qing|....}.
I want these files to be categorized into the category above.
My editsto {ACCcategory} don't seems to work. Any idea ? Is it the cache ? Yug (talk) 16:26, 15 September 2020 (UTC)[reply]

Comfirm me if this is right. I see on File:垣-bronze-warring.svg the style being provided via *2* fields, then I would need something such as {ACClicense|禾|clerical|han|....} and {ACClicense|禾|clerical|qing|....}, I see.... Yug (talk) 16:44, 15 September 2020 (UTC)[reply]

Hello again, I wanted the create review category but I'am realizing ACClicense already has plenty of conditional categorizations doing the work. Since you are my reference for ACC templating and ACC categories, could you tell me if this is needed or how to tag a character for general review or for sources check ?

• {{ACC character to review}} ←→ Category:ACC character to review. I expected to add some guiding text to the template so it becomes a proper ribbon.

I also created a template to tag the main categories (styles) with some ACC guidances :

• {{ACC category|intro=}}. Ex: Category:Spring and Autumn bronze script characters, I plan to have them get more elegant frames.

This reminds us of :

• {{ACC|頁}}. Ex: Category:ACC containing 頁

But I feel I may be pushing for something which you already create an I'am just not aware of it. What do you think of those above ? Yug (talk) 17:11, 15 September 2020 (UTC)[reply]

Thank you for your efforts! I feel ACC files in ACC top categories like Category:Bronze script characters or maintenance categories like Category:ACC needing time period are generally ACC characters for review. I think they are great, I will adapt those changes and upload new files following those standards. --Wargaz (talk) 17:32, 16 September 2020 (UTC)[reply]

I want you to upload svg seal script files of 割, 害, https://db.itkc.or.kr/data/imagedb/IMGHJ/MO_0593A_A272_433B_030_24.GIF, https://db.itkc.or.kr/data/imagedb/IMGHJ/MO_0593A_A272_433B_050_24.GIF, https://db.itkc.or.kr/data/imagedb/IMGHJ/MO_0593A_A272_433B_060_24.GIF, 觀, 勸, https://db.itkc.or.kr/data/imagedb/IMGHJ/MO_0593A_A272_433B_110_24.GIF, https://db.itkc.or.kr/data/imagedb/IMGHJ/MO_0593A_A272_433B_130_24.GIF, https://db.itkc.or.kr/data/imagedb/IMGHJ/MO_0593A_A272_433B_140_24.GIF, https://db.itkc.or.kr/data/imagedb/IMGHJ/MO_0593A_A272_433B_150_24.GIF, https://db.itkc.or.kr/data/imagedb/IMGHJ/MO_0593A_A272_433B_160_24.GIF, https://db.itkc.or.kr/data/imagedb/IMGHJ/MO_0593A_A272_433B_170_24.GIF Blahhmosh (talk) 17:09, 14 June 2024 (UTC)[reply]