User talk:LiliCharlie

From Wikimedia Commons, the free media repository
Jump to: navigation, search

SVG of Nôm character U+2B1A1[edit]

Could you make another Han-Nom svg: 𫆡 (U+2B1A1). I know Babelstone doesn't believe in making images for encoded characters. But very few readers can view Extension C characters otherwise. Not only that, but I can't use vi-nom on the Vietnamese Wiki. Kauffner (talk) 11:18, 16 December 2013 (UTC)

File name is “Nom Character U+2B1A1.svg”
1. When writing articles on simple.WP, imagine you are explaining the world to a young child. — 2. The ideographic description of is ⿱父巴 (top to bottom), not ⿰父巴 (left to right). —LiliCharlie (talk) 20:40, 16 December 2013 (UTC)
Could you make the change yourself? The edit history would look better if more than one person was involved. I noticed that càng (U+2B2D9), giàu (V04-405E) and béo (V+604ea) are in en:Chữ nôm. I checked several Nôm dictionaries, including Truong and Le's 19,000-character doorstop. But I didn't find any of these characters. So I don't think they should be presented as Nôm characters. They could be the equivalent of typos that somebody found in a manuscript. On another issue, do you think it would be a good idea to put vi-nom on Vietnamese Wiki? Kauffner (talk) 02:52, 17 December 2013 (UTC)

Shuowen Jiezi radicals[edit]

Thank you for your pictures of Shuowen Jiezi radicals. Great job! I used them in the article List of Shuowen Jiezi radicals (russian version), if you don't mind. --Dimitrius (talk) 09:21, 26 December 2013 (UTC)

Troublesome Extension C character[edit]

U+2A74C (𪝌) is supposed to look like ⿰亻𤰻. Or so says the Nom Foundation and the Chinese Text Project. Check out Fileformat, which gives me different results depending on what browser and system I use. Any idea what the problem is? Note that VNPF gives the radical/stroke count as 9.9, while Unihan and CTP give 9.10. I assume this character is a manuscript variant of 備. Kauffner (talk) 18:27, 4 January 2014 (UTC)

File name is “Nom Character U+2A74C.svg”
1. On my system all browsers except IE show the same character shape on the Fileformat page. I tested Firefox, Opera, IE and Crome. IE didn’t show any character.
2. The sources all say 𪝌 is radical 人/亻+ 9 strokes. (On the Unihan page look for the box with data type kRSUnicode.)
3. Ideographic description of 𪝌 as ⿰亻𤰻 is clearly correct.
4. Judging from the Vietnamese readings given by the Nom Foundation 𪝌 should be some variant of (=⿰亻𤰇) in Vietnamese, at least in certain words and phrases. Note however that this Unicode character also has a T-source, and whatever 𪝌 is used for in Taiwan it need not be a variant of the common character 備 there. LiliCharlie (talk) 20:13, 4 January 2014 (UTC)
P.S.: The font HAN NOM B has the wrong character encoded at u+2A74C; it shows ⿰木汁 instead of ⿰亻𤰻. Care should be taken to use the template {{Vi-nom-CJK-C-D}} instead of {{Vi-nom}} for characters of extensions C and D, because they differ in the fonts listed in their source code. LiliCharlie (talk) 22:56, 4 January 2014 (UTC)
So ⿰木汁 must be some PUA character floating around in HAN NOM B, encoded before Extension C existed. I wonder what it is. I put the svg you made into simple:Sino-Vietnamese characters. The bottom line seems to be that Extension C is still not ready for prime time. Kauffner (talk) 02:36, 5 January 2014 (UTC)
No, the bottom line is that HAN NOM B only covers Extension B and the other characters are “fillers used by font designers on purpose.” LiliCharlie (talk) 02:44, 6 January 2014 (UTC)


Hi LiliCharlie, you uploaded a lot of Chinese letters, e.g. The 214 Kangxi radicals in the dictionary’s own style (in SVG format), and others. May be you don't know yet, each Chinese character should be properly categorized. I did it just for one of your graphics, for Kangxi Style Kangxi Radical 009.svg, with {{Rcat}} which is IMHO the best possibility. As a suggestion, I licensed it also for {{PD-Unicode}} which seemded better than the license you took.
The necessary categorization will best be done by a bot. If you need more explanation or some hints, you may ask me. But please care for the categorization, anyway. sarang사랑 12:21, 16 February 2014 (UTC)

As a font designer I contest the claim that all representations of Unicode characters are per se in the public domain. The glyphs of my typefaces aren’t. Please allow me to continue selling the fonts I designed and revert your edits. LiliCharlie (talk) 13:02, 16 February 2014 (UTC)
Of course, if its your development, and a font designed by you, the license belongs to you; please forget my suggestion.
Another thing is the categorization of the radicals, not only to your font, but additional to all the single radical categories. This should be done for all glyphs representing a radical or a variation of it. sarang사랑 08:06, 18 February 2014 (UTC)
I noticed this when I was checking this page before unwatching it. FYI, the tag in question would be for bitmap versions of glyphs, not SVGs. Bitmap representations of fonts cannot be copyrighted in the U.S., but vector versions can be. The difference is that one is just an image, while the other are the actual programmatic instructions on how to make the font. The program is copyrightable; the actual typeface is not. That said, typefaces are patentable, so if you are worried about the ability to sell your fonts, you might want to consider doing that. Trlkly (talk) 22:33, 9 June 2014 (UTC)

Picture of the Year 2013 R2 Announcement[edit]

Round 2 of Picture of the Year 2013 is open![edit]

2012 Picture of the Year: A pair of European Bee-eaters in Ariège, France.

Dear Wikimedians,

Wikimedia Commons is happy to announce that the second round of the 2013 Picture of the Year competition is now open. This year will be the eighth edition of the annual Wikimedia Commons photo competition, which recognizes exceptional contributions by users on Wikimedia Commons. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2013) to produce a single Picture of the Year.

Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year were entered in this competition. These images include professional animal and plant shots, breathtaking panoramas and skylines, restorations of historical images, photographs portraying the world's best architecture, impressive human portraits, and so much more.

There are two total rounds of voting. In the first round, you voted for as many images as you liked. The top 30 overall and the most popular image in each category have continued to the final. In the final round, you may vote for just one image to become the Picture of the Year.

Round 2 will end on . Click here to learn more and vote »

the Wikimedia Commons Picture of the Year committee

You are receiving this message because you voted in the 2013 Picture of the Year contest.

This Picture of the Year vote notification was delivered by MediaWiki message delivery (talk) 19:22, 22 February 2014 (UTC)

About Logographic Vietnamese Terminology.svg[edit]

chữ Hán = chữ Nho = Hán tự;

Hán Nôm = chữ Hán + chữ Nôm

Please make sure the definition of each term. Thanks.-서공/Tây Cống/セイコゥ (talk) 03:10, 25 February 2014 (UTC)

This is just an illustration of how the terms are written using Nôm characters (with corresponding Quốc ngữ). An explanation of the terminology should be given in the Wiki projects that use this image. At this point the German, English, Spanish, French, Italian, Japanese, Dutch and Portuguese Wikipedias use it, and if I modify its contents these articles will need modification without their authors knowing that it does – there would be no warning, as no edits are made to the articles themselves. This doesn’t seem a good idea, does it? LiliCharlie (talk) 03:36, 25 February 2014 (UTC)
The explanation under the picture should be modified, as the first 3 words have the same meaning but the last one is different. --서공/Tây Cống/セイコゥ (talk) 05:12, 25 February 2014 (UTC)
What I uploaded is community-owned, not my private property, and I am not a Nôm expert either. Being part of our community you are invited to edit this explanation in any way that helps users understand what is shown. Of course you can also add explanations in other languages if you like. If the words in different languages do not exactly match it doesn’t really matter; someone can improve some particular translations later. Thanks for your interest, BTW. LiliCharlie (talk) 10:26, 25 February 2014 (UTC)

Picture of the Year 2013 Results Announcement[edit]

Picture of the Year 2013 Results[edit]

The 2013 Picture of the Year. View all results »

Dear LiliCharlie,

The 2013 Picture of the Year competition has ended and we are pleased to announce the results: We shattered participation records this year — more people voted in Picture of the Year 2013 than ever before. In both rounds, 4070 different people voted for their favorite images. Additionally, there were more image candidates (featured pictures) in the contest than ever before (962 images total).

  • In the first round, 2852 people voted for all 962 files
  • In the second round, 2919 people voted for the 50 finalists (the top 30 overall and top 2 in each category)

We congratulate the winners of the contest and thank them for creating these beautiful images and sharing them as freely licensed content:

  1. 157 people voted for the winner, an image of a lightbulb with the tungsten filament smoking and burning.
  2. In second place, 155 people voted for an image of "Sviati Hory" (Holy Mountains) National Park in Donetsk Oblast, Ukraine.
  3. In third place, 131 people voted for an image of a swallow flying and drinking.

Click here to view the top images »

We also sincerely thank to all 4070 voters for participating and we hope you will return for next year's contest in early 2015. We invite you to continue to participate in the Commons community by sharing your work.

the Picture of the Year committee

You are receiving this message because you voted in the 2013 Picture of the Year contest.

Delivered by MediaWiki message delivery (talk) 23:00, 26 March 2014 (UTC)

User page[edit]

A little too many pictures on your user page I think. It crashed my Chrome and froze Firefox for about 20 or 30 seconds. Safari seems to have no trouble with it though -- well done Safari! — Lfdder (talk) 13:21, 27 March 2014 (UTC)

I wasn’t aware that my user page caused such trouble. It has grown too long anyway, and I will split it into several sub-pages some day soon. Thanks for your hint. LiliCharlie (talk) 13:32, 27 March 2014 (UTC)

Which tool[edit]

Hi, you created a lot of fine SVG pics, e.g. the Kangxi and the Shuowen. I assume that you used a tool, like Inkscape+Scour, or something else, but I cannot find out. Would you mind to tell me? sarang사랑 07:35, 14 April 2014 (UTC)

I usually use (a developer version of) Inkscape, but I also frequently edit my SVGs in a text editor. Notepad++ allows bulk replacements for hundreds of files. — Und gerade habe ich bei einem Blick zwei Zeilen nach oben festgestellt, dass du ja auf eine Benutzerseite von de.WP linkst, wo steht, dass deine Muttersprache Deutsch ist. Die haben wir gemein. Greetings from Cologne, LiliCharlie (talk) 09:54, 14 April 2014 (UTC)

Diese Entwicklerversion scheint recht effizienten, fast redundanzfreien Code zu erzeugen, oder musst du nachträglich noch den Code glätten? Ich denke die Kombination Inkscape plus Notepad++ ist optimal für SVG-Code. Ich verwende schon lange Notepad++ aber längst noch nicht alles was dieser Editor kann. Mir macht er noch Probleme weil ich ihm einfach nicht verklickern kann dass er exotischere Fonts akzeptiert, er kennt diese Zeichen nicht und macht draus "?". Wahrscheinlich geht das ganz einfach zu vereinbaren wenn man weiss wie. Gruss an den Rhein! sarang사랑 12:07, 14 April 2014 (UTC)

Mit Inkscape speichere ich hochzuladende Grafiken nicht als Inkscape SVG (*.svg) sondern als Optimised SVG (*.svg) und schmeiße da alle von mir nicht gewünschten Informationen raus. Später entferne ich noch die wenigen verbliebenen überflüssigen Informationen mit Notepad++, in der Regel gleich für viele SGVs auf einen Schlag, was perfekt geht, da in allen genau derselbe Ballast verblieben ist.
Das mit den Fragezeichen in Notepad++ hört sich für mich so an, dass nicht der richtige Zeichensatz gewählt wurde (Menü: Encoding/Kodierung). Ist die Datei z. B. für den „ANSI“-Zeichensatz (d. h. ISO 8859-1) kodiert, so können auch keine exotischen, nicht in ISO 8859-1 vorhandenen Zeichen angezeigt oder gespeichert werden. — Meine Standard-Kodierung für neue Dateien ist UTF-8 (eine Kodierung des internationalen Unicode-Zeichensatzes) mit einem BOM, das Programmen, die die Datei öffnen, die Kodierung verrät (Menü: Settings/Einstellungen → Preferences/Optionen → New Document/Neue Dateien → UTF-8). — Bildschirm-Schriftarten werden über Settings/Einstellungen → Style Configurator/Stile eingestellt, aber das dürfte dein Problem nicht lösen, da bei im gewählten Font fehlenden Zeichen keine Fragezeichen dargestellt werden sollten, sondern Zeichen aus einem Font, den das Betriebssystem aufgrund der verfügbaren PANOSE-Informationen (oder wenn vorhanden der Schriftenersetzungs-Einträge in der Registry) auswählt. — Entschuldige diese ziemlich technischen Betrachtungen mit ebensolchen Links; im Endeffekt gilt aber: Probieren geht über studieren. Ganz liebe Grüße zurück ins Schwabenland, LiliCharlie (talk) 05:07, 15 April 2014 (UTC)

Danke für den Expertenrat! Ich werde es demnächst versuchen, du lieferst mir ja ein sehr brauchbares Rezept. Das meiste ist mir bekannt, aber in Bezug auf Notepad habe ich die Anwendung zur Änderung der Grundeinstellungen nicht gleich hinbekommen und es dann gelassen. Nun werde ich sehen das richtig zu machen. Gruss sarang사랑 16:06, 15 April 2014 (UTC)

Path text SVG for Welcomes[edit]

While I really think your Welcome images are awesome, they would be even better if you would not convert the text to path. As you can see, at least one of your images is listed at .

I realize that finding the fonts so you can test them on your system can be difficult. But if you'll use Arial, it will usually work out, even if the image will look a little different. (The Arial will be replaced with Liberation Sans.)

You don't have to use text for the the non-alphabetic ones if they cause you problems (Like Chinese or sign language). But text would be a lot better for all the rest. Cheers. Trlkly (talk) 08:53, 15 April 2014 (UTC)

I don’t consider these images to convey a purely textual message, as in a map or a statistician’s chart. Rather I have chosen fonts that convey a warm, welcoming sentiment. Both Arial and Liberation Sans are far too matter-of-fact and spoil the message. It is best to regard the images as pieces of art that shouldn’t be forged.
On the other hand I understand the advantages of embedded text. (Cf. what I wrote 2½ weeks ago on this talk page.) All I can offer at this point is uploading additional versions in PDF format, with embedded text and a much reduced file size — for all practical purposes the only drawback is the background isn’t transparent. How about that? LiliCharlie (talk) 03:39, 17 April 2014 (UTC)
Unfortunately, a PDF with embedded fonts would probably still be a problem, as only free fonts can be uploaded here for copyright reasons, and at least some of your fonts don't seem to be free (as in liberty--e.g. open source). If you can't find a suitable font in the list of Wikimedia's fonts, the usual workaround is a bit more complicated.
What you do is duplicate every text object. You leave one as text, but convert the other to path. Then you hide all the text elements. Yes, the file is still large, but that's not the point of including text. You include it so it's easy for others to modify and make their own stuff. That's part of the point of Wikimedia commons. We host images that you are free to do whatever you want with.
If the actual text is hidden, it won't matter if it says to use a font that Wikimedia doesn't have. But it allows the actual text to be available in the file for easy modification. Trlkly (talk) 07:10, 20 April 2014 (UTC)
I have already uploaded PDF versions of these images. They are text versions with embedded font (the default for PDF), so it is possible to copy text from them, or edit it. Unfortunately the MediaWiki software renders PDFs rather poorly, but I hope it will be replaced by better rendering software before long.
I’ve never produced an SVG that has the same information as both path and text. Do you mean I should include the text elements in a comment (between <!-- and -->), or is there another way to hide them? LiliCharlie (talk) 07:44, 20 April 2014 (UTC)
Yes, there's another way to hide them. I'm not sure which editor you use, but, in Inkscape, you right click an object, choose Properties, and click the "hide" checkbox. In Illustrator, you can click on the eye icon in the objects panel. If you are editing by hand, you add "visibility:hidden" to the style attribute.
As for your PDFs, I'm just worried that they may get deleted in the future for containing embedded non-free fonts. Plus Commons really prefers SVGs for images, using PDFs for documents. Trlkly (talk) 09:49, 25 April 2014 (UTC)