How to change squad number fifa 14

Template talk: COA information

Replacing {{Blason-fr-en-it}} by this template [edit]

See Template talk: Blason-fr-en-it

Don't you think that {{COAInformation}} should be easier to use by any contributor for any coat of arms? Thus there should be another template ({{COAInformation / fr}}?), That would be specific for contributors to the Blazon Project of French-speaking Wikipedia (with specific parameters and categorization pattern coming from {{Blason-fr-en-it }}). - Gypsies 11:14, 14 November 2007 (UTC)

2014 [edit]

 

It has been suggested that this talk page should be merged with template: Blason-fr-en-it. (discuss)
Reason: There is no reason for several COA information templates. The template is completely redundant and more it restricts more information.User: Perhelion (Commons: = crap?)11:47, 28 July 2014 (UTC)

Probably a good idea, but shouldn't be done in a heavy-handed way which autogenerates warning messages on every image which formerly used the old template ... AnonMoos (talk) 23:51, 28 July 2014 (UTC)

Documentation [edit]

When you update this template, such as adding German language and making "SVG COA of France" not automatic. Then please also update the documentation page. / Local_Profil 17:43, 19 November 2007 (UTC)

I don't understand, since I did upload the documentation page. Maybe you talk about the "usage example", that I forgot to upload?
Anyway, I created {{COAInformation / fr}}, which is specific to fr-Blazon Project, and with the same parameters as {{Blason-fr-en-it}}. So I will upload {{COAInformation}} to make it easier to use.
Gypsies 19:21, 19 November 2007 (UTC)
Sorry I think managed to start writing the above message whilst you were updating the documentation. Sorry for being hasty. / Local_Profile 21:32, 19 November 2007 (UTC)
No problem ! I am too much slow :-) Gypsy 22:03, 19 November 2007 (UTC)

Deletion of parameters related to the fr-Blazon Project [edit]

After the creation of {{COAInformation / fr}}, the following changes have been done in {{COAInformation}}:

  • Source: "Own work / Oeuvre personnelle / Obra personal" is not written by default
  • Source: The parameters "sourceen", "sourcefr" and "sourceit" do not exist anymore
  • Author: The parameter "dessinateur" does not exist anymore
  • Author: The box "Blazon Project" does not appear by default
  • Category: The Category: SVG coats of arms - France is no more added by default
If you don't mind me asking. Why didd you remove the "sourceen", "sourcefr" and "sourceit"? I fail to see how these were specific to fr-Blazon Project. / Local_Profil 21:38, 19 November 2007 (UTC)
They were useful in a template aimed at replace {{Blason-fr-en-it}} (they were the only source fields in this template). That's why they remain in {{COAInformation / fr}}. I prefered delete them in {{COAInformation}} since I thought they made the usage indications more complex, and they were not much useful (they can easily be added manually).
If you think I'm wrong, please revert this modification. Gypsies 22:10, 19 November 2007 (UTC)
No you're right, guess I just never really thought of why they were there. I've made changes to COAInformation / fr so that it uses COAInformation (in case we want to make changes to it in the future) it still works in the exact same way as before though with the same specific parameters. / Local_Profil 00:14, 20 November 2007 (UTC)

My changes [edit]

OK, since the fr-Blazon Project has splintered of from this template I took the liberty to finally move the categories outside the template. The reference to how to add them is still there the only difference is that they are now added explicitly after the template instead of as parameters inside the template. Whilst att it I also modified the Inkscape tag. now instead of adding the noink parameter to remove the inkscape tag you now have to add the ink parameter to add the tag, it makes more sense to me to not assume that everyone uses inkscape. I've also updated the documentation to reflect the changes but I've not updated the French section since although I read French I would not claim to be able to write in French. As always if anyone has any opinions, comments just shout =) / Lokal_Profil 23:46, 19 November 2007 (UTC)

That's good. I've uploaded the French sections. Gypsies 09:16, 20 November 2007 (UTC)

Problem with Finnish and Swedish versions [edit]

Moved from User talk: Care, by Zigeuner (talk) 21:55, 3 February 2009 (UTC):

The Finnish fields are now available. You can use the template if you desire.
Example:
Date January 24, 2009
artistCare. Original design by Ahti Hammar.
Source Own work
Permission
(Reusing this file)
See below
Now eveything os OK! Gypsies (talk) 22:49, 24 January 2009 (UTC)
Thanks. I tested this with File: Närpiö.vaakuna.svg and basically it works fine. However, because of the nature of Finnish, blasonfi-field does not work very fluently. The current wording is similar to saying it in English as 'Pyhtää of coat of arms' (i.e. reversed genetic). I am wondering, could this blason field actually be reformatted with colspan to fill in both columns? So in English, this single field would be 'Coat of arms of {{{blasonen}}}', but in Finnish '{{{blasonfi}}} vaakuna'. I also see the same issue in Swedish, where they are using '{{{blasonsv}}} vapen'. Just leaving this into your consideration. --Care (talk) 23:59, 24 January 2009 (UTC)
I think a better way would be to replace (in every languages) the field "Coat of arms of" by something like "Bearer" or "Holder". What do you think about that? If you agree what are the translation of "bearer" in Finnish and Swedish?
Gypsies (talk) 12:12, 25 January 2009 (UTC)
This might work with family arms in Finnish (even though I am not quite sure of correct wording - even local registry is referring to this as 'person who has right to use the CoA'), but in my understanding similar wording for municipalities / provinces simply does not exist without sounding ridiculous. I could be wrong, but at least I cannot come up with good translation in Finnish. --Care (talk) 12:59, 25 January 2009 (UTC)
Well, I don't know what to do ... I think it is better that in each language there is the same things at the same place.
Maybe it could be better to add automatically the word "vaakuna" after the blasonfi-field? Gypsies (talk) 00:37, 30 January 2009 (UTC)
I do not really know. I was thinking something like this, but that "vaakuna" could work as well, even though there is additional repetition. in wording. --Care (talk) 09:27, 30 January 2009 (UTC)
I tried something in the way you were thinking. Look in the example above (maybe you will have to refresh your page). I tried that the CoaInfobox look the same in each language. The empty field (instead of "Vaakuna") may be replaced by something like "Coat of arms represented" (in Finnish and Swedish). Gypsies (talk) 15:04, 30 January 2009 (UTC)
Can you make the first row to be just a single row with colspan = "2"? Personally, I prefer the previous version over the current one as now it looks like row titles are missing in sv and fi. --Care (talk) 20:04, 30 January 2009 (UTC)
To avoid that titles are missing, I proposed to write "Represented coat of arms" (fi / sv translation needed). Don't you agree with this idea? Gypsies (talk) 21:35, 31 January 2009 (UTC)
I am sorry, but I am really out of ideas how that could be presented with fluent Finnish (even though I know word-by-word translation). I guess the term as such is foreign to our language, and we are just saying them to be somebody's coat of arms. If you are unwilling to do that colspan-stuff, the initial version is then the best one for Finnish. Thanks. --Care (talk) 00:47, February 1, 2009 (UTC)
So, back to the initial version. It seems to be the best compromise. I am also sorry, but I'm very surprised there is no Finnish translation of "Represented coat of arms" (i.e. "Coat of arms that are shown here"). I think this discussion should be copied in the talk page of the template; so maybe somebody else will find a better version of the template. Gypsies (talk) 21:41, 3 February 2009 (UTC)

If somebody find something better ... Zigeuner (talk) 21:55, 3 February 2009 (UTC)

When adding the Hungarian language (and additionally Esperanto) I encountered a similar problem to what we had with Finnish, the word for coat of arms postponed to the name of the armiger, címere in Hungarian and vaakuna in Finnish. To avoid doubling I inserted the word for file (fájl in Hungarian and tiedosto in Finnish) at the beginning. Or do you think it would be better to insert the words for image?
--ludger1961 (talk) 03:49, 7 September 2009 (UTC)

Additional languages ​​from the Iberian Peninsula [edit]

During my categorization works for files with coats of arms I regularly stumble about files contributed from our friends from the Iberian Peninsula, with blazons in their different official languages. Great thanks not only for the Taller de Heráldica y Vexilología in the Spanish Wikipedia and their numerous contributors like SanchoPanzaXXI and Xavigivax, to name at least some of them. So I felt the great need to add those languages, namely Catalan, Spanish, Galician and Portuguese, to this template. Look at the example below, other improvements welcome.
Best wishes --ludger1961 (talk) 08:10, 5 September 2009 (UTC)

need 9 source figure [edit]

I need to have figure9 for this file =

I tryed to do it myself but doesn't work. Need help please. --Titimaster (talk) 11:52, 29 August 2011 (UTC)

AttribSVG [edit]

I'm not going to experiment with this, in fear of messing something up. Template: AttribSVG autotranslates. Can that be used (or adapted), instead of the current permanently bilingual template? Lemmens, Tom (talk) 15:35, 30 September 2013 (UTC)


The following paragraphs show the brainstorming

of several users in the effort to make things
better, in this case the file descriptions.

Sorry it was German people, talking German.

Template talk: Created with Inkscape - Edit request [edit]

We - that's Juergenk59 and I - followed your work on the templates with great interest. We also have a request that you could help us with with your experience in implementation. In the current version, I can add more text. Since we generally design all coats of arms drawn by us with colors according to the FIAV standard, we add the text here as in the example: Colors according to FIAV: This image was created with Inkscape. Colors according to FIAV. Our wish would be to achieve this directly with the supplement. Do you think you could support this? --Maxxl2 - talk 09:02, 10 May 2014 (UTC)

Yes, absolutely. But at first glance it doesn't seem to me that it is in the right place in {{Inkscape}} etc., IMHO it belongs in the file description; I can imagine a template that does this with the parameter of {{Information}} (using {{InFi}} internally). A standard text would then be easier to modify using parameters. OK?
BTW: the data in DEU Oeslau COA.svg cause the categorization according to Created with Inkscape and according to Valid SVG. Since my change / extension, created with Inkscape is categorized with only after Valid SVG, this category is then categorized into the two categories - a significant relief of the two stressed other categories. In the case of these COAs, I would even sub-categorize in order to differentiate further. sarang♥ 사랑 09:24, 10 May 2014 (UTC)
Categorization: Did I understand you correctly that you would prefer a sub-category COA?
: you never stop learning. We have not yet seen this possibility (in four years). With six or seven colors, it'll be a pretty big chunk. Is that also possible a little slimmer? --Maxxl2 - talk 10:00, 10 May 2014 (UTC)
Valid SVG created with Inkscape already has a few sub-cats. Depending on the number of candidates or on the thematic assignment, such a sub-grouping makes sense. Should be considered and coordinated beforehand (I subsequently classified what was already there). It may also be possible to do this using a template, but it can also be done directly (parameter "sub").
If you all If you want to specify colors, the {{Tbc}} table may be a big block. Since you almost never have to specify Pantone colors, this could also be streamlined, for example several colors in one line, and then directly with hexadecimal values. We can think of something there.
# 00F# F00# F0For, another examplelime = # 0F0# FF0 = gold
Only "Colors according to FIAV"It's easier to spend, of course. sarang♥ 사랑 10:31, 10 May 2014 (UTC)
Unfortunately does not work in the {{COAInformation}}. I have the color table in the example here
orrendered as
argentrendered as
azurerendered as
gulesrendered as
purplerendered as
sablerendered as
vertrendered as
therefore built under. If only you could reduce the line height to 20px / 1em. Got another idea? --Maxxl2 - talk 10:39, 10 May 2014 (UTC)
I quickly put it in the "COA information". This template is already categorized into its own sub-category, with 3800 files. See if you'd rather have the colors above or below. There would even be another one that I can show you quickly. sarang♥ 사랑 10:50, 10 May 2014 (UTC)
Great - immediately renamed it. The position at the end of the COA information is better, but it should be in front. If the cell height were now reduced to half, it would be optimal. Is that still possible? --Maxxl2 - talk 11:01, 10 May 2014 (UTC)
Everything can be done. The position of is fixed, at the end, also, before the date, but since it all runs through {{COAInformation}}, a lot can be done. I'll have a look at it today and then let you know. It won't be quick now, but assume that I can find a solution. But for now, wait with the installation in 10000 files! sarang♥ 사랑 11:23, 10 May 2014 (UTC)
No problem - I'll wait patiently. For the next few weeks, I'm mainly busy with route maps and stage profiles for the Giro d'Italia and the Tour de France. --Maxxl2 - talk 11:32, 10 May 2014 (UTC)
The colors can easily be integrated between Author and other_versions - or anywhere else. Is made in 'COAInformation' and can therefore easily be changed again. Essential question: is the number of colors limited or small? The SVG image has about 12 main colors and then associated secondary colors; the other picture has more.
Wikiproyecto: Ilustración / Taller de Heráldica y Vexilología / Convenciones para banderas lists them.
I have in mind that every color gets a letter, for example, whereby the assignment will be in the preferred language, most likely French tinctures (or, argent; azure, gules, purple, sable, vert). Would that be feasible? Tell me what you need sarang♥ 사랑 12:24, 10 May 2014 (UTC)

@Perhelion: - please read along :)

That looks good. Here is our color palette, which is completely sufficient. Exceptions are referenced separately. --Maxxl2 - talk 12:37, 10 May 2014 (UTC)
The language for the colors is English, i.e. the first color name in the table is the correct one. --Maxxl2 - talk 12:44, 10 May 2014 (UTC)
      • Which table now? The GIMP palette with 13 colors? Nowhere is that first color name English. sarang♥ 사랑
I admit, the English heraldry color names do not sound "Anglo-Saxon" because they are of Norman (French) origin. But these are: Sable - Argent - Argent (dark) - Gules - Or - Azure - Bleu celeste - Bleu celeste (alt.) - Vert - Carnation - Purpure - Tawny - Cendrée. --Maxxl2 - talk 14:30, 10 May 2014 (UTC)
There are two different things at stake here:
  1. How do I tell the template; IMHO this should be done with a few entries, after all, nobody should break their fingers and type long names. One letter for the standard colors is completely sufficient (max. Two). And special colors have to be described with the hexa color code, possibly also with color names.
  2. The second is the implementation in the template. This can be expanded, expanded and / or changed if necessary, different (table) format, etc., everything is independent of the information in the individual file descriptions.
First of all, we have to determine which parameters are to be transferred and how. The example above with the FIFG template is a first suggestion.
For the Exceptions it might make sense to only specify the color value (# 623 or # A1B285) instead of the standard color code (g, b, r, ...) and, if necessary, to add text below the table. Whereby, for example Ermine pattern is two-tone, if necessary a solution can also be found there, how this is processed. So enough to clarify in advance! sarang♥ 사랑 14:38, 10 May 2014 (UTC)
With these 13 colors we have 3 × the "A", and 2 × each of the "B" and the "C". If you like the one-letter parameterization, we have to agree something sensible on how we can avoid this dilemma. It's all about communicating this to the template - a German coat of arms workshop can also take abbreviations from another language or mix them.
"Cendrée" can do the template output, but it shouldn't have to be entered as text every time. sarang♥ 사랑 14:46, 10 May 2014 (UTC)
Is "case sensitive" possible? --Maxxl2 - talk 15:03, 10 May 2014 (UTC)
Sable = S - Argent = A - Argent (dark) = a - Gules = G - Or = O - Azure = B - Bleu celeste = b - Bleu celeste (alt.) = C - Vert = V - Carnation = - Purpure = P - Tawny = T. Like this? --Maxxl2 - talk 15:07, 10 May 2014 (UTC)
This is possible and is extremely easy to program in the template. But it is even more important that the heraldic draftsman and picture writer does not have to make any mental contortions and always look in the cookbook. For the If it should be simple and self-explanatory, everything can be programmed. I think more lowercase letters are better, aren't they easier to enter?
I said something about Sassnitz above. sarang♥ 사랑 16:26, 10 May 2014 (UTC)
The idea was as follows: the main colors all have capital letters, the secondary colors (deviations) have minuscules. The only exception to the common color names is Azure = B (lue). But if you think it's more common, we can invert the scheme:
  • Sable = s - Argent = a - Argent (dark) = A - Gules = g - Or = o - Azure = b(lue) - Bleu celeste = B - Bleu celeste (alt.) = C(eleste) - Vert = v - Carnation = c - Purpure = p - Tawny = t.
What I see is that the lowercase letters are easier to type. So let's do that. Is easier to use. --Maxxl2 - talk 16:40, 10 May 2014 (UTC)

"Source" field in the "Information" template [edit]

What I've always wanted to know: why are both the "Inkscape" and "W3C" templates displayed in this field? Both templates do not concern the sources from the literature or the Internet, but rather belong to the "Description" or the "Author", especially because he is mentioned again in "Created with Inkscape". Or is that a reference back to {{own}} in the source? --Maxxl2 - talk 11:28, 10 May 2014 (UTC)

The position can be freely assigned in {{COAInformation}}, I couldn't think of anything better in the rush. We can see where it fits better. And whether the author is mentioned again. That can all be improved! sarang♥ 사랑 11:32, 10 May 2014 (UTC)

FIAV colors [edit]

The template is not limited in the number of colors, the limit lies more in the short codes to be assigned. The colors can be changed later, also expanded. In the meantime I would like to know whether this is true so far, the tables are not so clear. The color hex code can be seen when the mouse pointer points to the color balls.

FIAV colors and the short codes
a = argentrendered as
A = argent darkrendered as
b = azurerendered as
B = Bleu Célesterendered as
c = carnationrendered as
C = cendréerendered as
g = gulesrendered as
o = orrendered as
p = purplerendered as
s = sablerendered as
t = tawnyrendered as
v = vertrendered as

sarang♥ 사랑 09:59, 12 May 2014 (UTC)

+1 - it's true. How will this be incorporated into the "Used colors according to FIAV" template? --Maxxl2 - talk 10:12, 12 May 2014 (UTC)
My idea: {{COAInformation}}, and any others, are extended by a parameter "colors =" (or something like that); how I'll do that, I'm still thinking about it. sarang♥ 사랑
Thank you for your commitment! I'm really excited ... Greetings --Juergenk59 (talk) 12:12, 12 May 2014 (UTC)

Now I am a little further and have got the biggest problem under control. Everything else is details to chat about. Eg should the new parameter for COA information be or? It is interesting how many tingings the template has to cope with, ie does the table have to have multiple lines? It could look something like this between and, at "":

000000FIAV colors:00gules000argent00 purple 00céleste00000or0000

Formatting such as. Line height, font, or if you want a thin frame around, all of this is possible. Is it okay so far? sarang♥ 사랑 14:44, 12 May 2014 (UTC)

If that is OK? Nah - that's great. Generated the whole palette from five letters, it couldn't be better. --Maxxl2 - talk 15:28, 12 May 2014 (UTC)
One request: we can instead of the American colors the English colors write. That fits better with the color names. --Maxxl2 - talk 15:31, 12 May 2014 (UTC)
Simply great! I can only join Maxxl2 there. We could also make friends with a thin frame around the Argent. There are seldom more than six colors in a coat of arms, so that the whole fits comfortably in one line. Thanks again. Greetings - Juergenk59 (talk) 16:02, 12 May 2014 (UTC)

As text: FIAV colors, as parameters: colors (because it's shorter); these are these details that can be changed quickly at any time (the parameter not if it is used 5000 times ...)
... "seldom more" is less in demand, I am interested in the maximum. As far as I am concerned, 800 colors, but if there are more than eight to 9 it has to be multiline. Can be done, even later. sarang♥ 사랑 16:11, 12 May 2014 (UTC)

We should say very clearly: a maximum of 9 colors, otherwise it will fray and is no longer important. If a flesh-colored rose blooms somewhere in the background on a meadow, we can do without this. This is then no longer classic heraldry. --Maxxl2 - talk 16:29, 12 May 2014 (UTC)
We had one more thought: if "" is also possible then "" without "pipes"?
PS: Why is suddenly case sensitive to "Author", "Source" etc. so values ​​from "author", "source" etc. are not adopted? --Maxxl2 - talk 17:22, 12 May 2014 (UTC)

Suddenly? So, I definitely got it Nothing rotated (can look in the history). {{Information}} has the parameters in all possible spellings, as you can see there, {{COAInformation}} only in upper case (except for the new parameters "other_" that I have added, which are inconsistently only effective in lower case for the time being ).
No, it doesn't work without pipes, that was my problem, the Wikipedia template logic allows no String operations, like other better macro languages. I'm really glad that I can do it with pipes! sarang♥ 사랑 17:36, 12 May 2014 (UTC)

Short technical excurs:

Everybody accustomed with the Wikipedia Template System
will immediately see that with, written
with the parameter of {{COAInformation}}, only the
first parameter ("a" in the example) is really a parameter of
- the first and only one. All the other parameters
values ​​(b, c, d, ...) or value parameters are in fact unnamed
parameters of the {{COAInformation}}, "b" the first one.

But it is not any problem to deal with this situation.

Sorry - no - not suddenly - is a general problem for me as long as I use both templates. It strikes me again and again when I turn {{Information}} into {{COAInformation}}. Then the data is only partially adopted. Only when I describe the parameters with capital letters in the first place will it work again.
Pipes: was just a question, not a requirement. --Maxxl2 - talk 17:43, 12 May 2014 (UTC)

All of this can be done if this convenience is desired. That author, author and, if you like, also author and authors are accepted.
A first version is ready soon, documentation will follow, it can then be incorporated into COA information from now on (colors is the name of the parameter, for the time being!). Can currently cope with 10 tinctures, the table row will be hanging on the right ... sarang♥ 사랑 17:50, 12 May 2014 (UTC)

Thank you thank you. We will first use it intensively, collect our experience and when practical experience shows that there are serious opportunities for improvement, we can talk about it again. --Maxxl2 - talk 17:56, 12 May 2014 (UTC)

Have a look before you say thank you! By the way, if that is too cumbersome with a-A, b-B etc., you can also use a-da and so, for example, with two letters, then even case-insensitive. I'll be the same. sarang♥ 사랑

Looks good. Could it be that "Permission", which was previously skipped if no information was given, is now displayed permanently? "
Will the author no longer be included in the {{Inkscape}}? --Maxxl2 - talk 18:15, 12 May 2014 (UTC)

Yes, that is still a mistake that the permission always comes. I'll do it. I took the author out because he’s right under it anyway.

You're right. Looks cleaner now. --Maxxl2 - talk 18:27, 12 May 2014 (UTC)

Release [edit]

It's not all right yet, but you can already try. We'll see then. Is the parameter right? Everything else can be changed centrally, only the calls with parameter names and the parameter letters cannot. Documentation will follow, have fun sarang♥ 사랑 18:18, 12 May 2014 (UTC)

"Permissions" are gone now, but I had to put the tinctures higher, between the author and any permissions. If nothing changes if permissions remain free, it is better to do it outside (with int: license-header) anyway. I'm still working on the line height. sarang♥ 사랑

That's right. We are very happy with it. I just discussed everything with Juergenk59 via Skype. --Maxxl2 - talk 18:49, 12 May 2014 (UTC)

Yes, making calls is much faster, and texts can also be sent in Skype if necessary. I had already considered proposing telephone contact for you. I have to clean up my talk page again, it has become huge again ... sarang♥ 사랑 18:55, 12 May 2014 (UTC)

With such extensive work here and now, we decided to skype. See you. --Maxxl2 - talk 19:03, 12 May 2014 (UTC)

I built the new option modularly, in {{FIAV2}} you can easily change something yourself, add tinctures if necessary. By the way, other colors can be specified instead of the letter directly a value #rgb or #rrggbb; Of course I don't have a name for it then. example

argentazurecarnation# F0Fgules# 22aa1cargent-d

(You won't need it, but helps as a test before adding new tinctures). I'll skype you, just like that. sarang♥ 사랑 19:07, 12 May 2014 (UTC)

Bug: with mouseover it outputs "#abc" for all colors. --Maxxl2 - talk 19:39, 12 May 2014 (UTC)

Thanks, it's fixed.
Is there actually an agreement for the order of the colors? For example, first the metals, then the others, or according to the surface area?
I have changed a few things about the COInformation: uppercase no longer has to be, and permission should be handled differently. I have adapted the documentation slightly, there is still a lot that can be done.

Do you want to revise all 6850 integrations of COAInfo ??? Then live a long life and have fun! Nothing works with bot, it has to be done manually. However, a lot could be repaired via bot if test categories were created, such as for Permissions. There is still a lot to be done, I'm sticking to it sarang♥ 사랑 05:35, 13 May 2014 (UTC)

Hello,
on the subject of color sequence - metals first - then alphabetically is the sorting. We "deschte no".
on the subject of the category - the two 5,000 and 6,000 heavyweights are no longer manageable. You have already suggested creating subcategories elsewhere. That has to be discussed and then one should dissolve the knowledge according to criteria such as geographical and design aspects. We try harder! - Maxxl2 - talk 06:06, 13 May 2014 (UTC)

Everything that can be done via bot remains a manageable effort. Since you can think of something, how such a bot could use info in the definition for it. As far as I saw, these things are pretty well categorized anyway. By test category I mean that, for example, everyone is placed in an additional maintenance category and the edits are carried out again.
In DEU district Rotenburg Wuemme COA.svg Jürgen does not follow this order. I also noticed that a categorization according to heraldic colors could also be done from our template, namely dynamically - can be activated and deactivated at any time. It would make sense to have those that are now available direct Remove categorizations via bot. sarang♥ 사랑 06:22, 13 May 2014 (UTC)

So far we have categorized each coat of arms by color / tincture. That also gave rise to voluminous categories. We then asked ourselves about the usefulness of these categories and unfortunately did not find any special ones for the reader. Therefore we dropped this categorization, Juergenk59 partially deleted saved categories. What I am seeing is making possible maintenance work on these tincture categories easier.
In general, I have the impression that Google has now also cut out the categories on Wikipedia as a finding aid for the reader. --Maxxl2 - talk 06:52, 13 May 2014 (UTC)

In case you want to take a look at the documentation, what I have put in so far: Template: FIAV1 / doc. I think to move these extensive discussions to the templates' talk pages, they seem to be in good hands there, and it's gone. sarang♥ 사랑 09:22, 13 May 2014 (UTC)

I made the font a little bigger, it was too small; And I managed to make the boxes a bit lower, but you can't get any narrower with the larger font (unless I make them different widths, which I don't like). Now I stop turning around as long as nothing is complained about.
In addition to a lot of cleanup, a bot could analyze

  1. what tincture categories a file has, then
  2. based on this, incorporate the new color legend, and
  3. remove the categories.

I haven't examined whether it's worth it, probably only if there are a corresponding number of COAs in the tincture categories (and that's correct), I might have a look. sarang♥ 사랑 09:37, 13 May 2014 (UTC)

If we need orange, rosé, murrey, sangiune, tenné etc. at some point, this can be added at any time. sarang♥ 사랑
I'm making the font smaller again, so far I haven't figured out how to fine-tune it.

For me, a general question arises when I look at the examples in WikiProjekt Wappen / Redrawing: If heraldically correct colors Not correspond to this FIAV range, what then? Should we leave five (or 9 or hex-B) straight and describe as if FIAV colors were used? Would be a bit questionable IMHO. Shall we tell the actual colors? Doesn't work so well with the new template (which is fixed on FIAV), {{Tbc}} would be suitable. It is definitely not an alternative to change the SVG coding in beautiful and correct coats of arms like DEU Schwerin COA.svg in order to achieve the invisible alignment to the FIAV colors azure and or (there are really more important things to do than thousands of graphics adapt, and FIAV is not the ultimate measure of all things).
So best close your eyes and FIAV - a note would be conceivable that there is only one equivalent and not exactly these Hecxodes are coded. sarang♥ 사랑 06:01, 14 May 2014 (UTC)
Let's look back for a moment where we came from. Our common concern arose from the endeavor to only allow valid SVG code in heraldic files and to mark it according to the creation method and editor. "In the wild" we of course find a large number of files that do not or still meet these requirements, but still meet a good information request. Establishing conformity is a long-term task.
The same applies to newly created coats of arms. We want to ensure that all newly vectorized coats of arms meet both requirements (W3C, editor information and FIAV certification). We also focus on D-A-CH coats of arms. In addition, it is obvious that the coats of arms we have created ourselves are initially adapted as part of a harmonization process. Step by step, we should then also approach the coats of arms created by third parties, although in the past we did not only do the description and sourcing, but also the execution in FIAV colors and a matching coat of arms. Whether FIFA or FIAV, both are the regulatory authorities that are "democratically" written and so the set of rules cannot be viewed as static.
For the exceptional cases you thankfully left enough legroom so that the FIAV bars can be expanded if the additional colors are compliant, otherwise the {{Tbc}} can be used. --Maxxl2 - talk 06:35, 14 May 2014 (UTC)
Now that I'll be forced to get involved, my comment :-P: I would argue that a link to the FIAV should be included in the description link (that's only available in small form with the normal info template for permission), there is also a small one Sense error, if you do not enter FIAV colors and FIAV is still there. Can you also do that flexibly? Otherwise really very nice - Perhelion (talk) 19:37, 16 May 2014 (UTC)
Yes, I am thinking of a named parameter for colors, eg "name =", so that any text (also with a link) can be set as a substitute for "FIAV colors". Or, so that not every coat of arms has a different text, instead of total flexibility just a yes / no parameter, which then outputs something like "Compare to FIAV" or "Used colors" instead. As soon as there is consensus on that, I'll put that in sarang♥ 사랑 11:48, 17 May 2014 (UTC)

Madboy colors [edit]

Hi, Sorry, but I reverted the Coa Illustration Tincture basic Purpure.svg because the color has been changed. I use a standard palette. Bye, Madboy74 (talk) 14:46, 19 May 2014 (UTC)

Very interesting news. Could you please give us a link to your standard palette. Thanks in advance. --Maxxl2 - talk 15:03, 19 May 2014 (UTC)
Hi Manfred, you can find Madboys standard at CoA illustration tincture. I expanded his table for a comparison with the FIAV colors. I am sure there are several standards for colors, and FIAV is IMHO neither the Pope itself, nor anyhow god-given or -inspired. So its the best solution to accept the other standards, and follow our own. sarang♥ 사랑 17:05, 19 May 2014 (UTC)
I am aware of at least 9 different color palettes applied in D-A-CH heraldry. Even more there is a Swedish one and I am sure many more national ones. That is why I am collecting the various palettes, personal ones or national standards. --Maxxl2 - talk 17:12, 19 May 2014 (UTC)
You are the expert, contrary to me. I suppose that there are also a lot of free style colorings? My first thought to "red" was # F00, to "yellow" # FF0 and so on for the other main colors (see the "simple colors" in Help: KF). But I see the world is not so simple as simple people believe ... sarang♥ 사랑 17:31, 19 May 2014 (UTC)
Hi,
Here is my gpl file:
GIMP palette
The latest palette from scanned Hungarian coat of arms, but optimizing the colors in every coat of arms not easy so this palette is under construction. In the future i will change to this palette.
Bye, Madboy74 (talk) 18:01, 19 May 2014 (UTC)
Color table conversion

converted into tables with hexadecimal notation

GIMP Palette Name: Heraldry
Whiterendered as
Sablerendered as
Orrendered asPantone 109 C
Workrendered asPantone 428 C
Gulesrendered asPantone 485 C
Azurerendered asPantone 286 C
Vertrendered asPantone 355 C
Purplerendered asPantone 247 C
Murreyrendered asPantone 208 C
Tennérendered asPantone 718 C
Cendrerendered asPantone Cool Gray 8
Sanguinerendered as
Tyrian Purplerendered asPantone 222 C
Light purplerendered asPantone 252 C
Middle Purple