text:
At other wikipedias, the  prefix links to the en.wiki article but isn't otherwise treated as a inter-language inter-wiki link.
 * —Trappist the monk (talk) 12:53, 5 August 2020 (UTC)
 * Regarding, "Inter-wiki links are apparently namespace sensitive", yes; see Help:Interlanguage links. And that's great that you were able to mock up something in the sandbox for the *-link case so quickly. I realize the other case (publisher, and other fields) is different, and is complicated by the legit shortcut codes that link to sister projects. Did anyone mention, , , ? See also, m:Help:Interwiki linking. Mathglot (talk) 09:35, 5 August 2020 (UTC) updated 10:21, 5 August 2020 (UTC)
 * I mentioned  earlier.
 * At present cs1|2 tests what it thinks is a prefix against the table of known inter-wiki prefixes returned from .  I am minded to change that and instead use the list of languages returned by   if I can show that all of the language codes in that list are also found in the inter-wiki map list.
 * —Trappist the monk (talk) 12:53, 5 August 2020 (UTC)
 * I have changed the code so that ~/Configuration/sandbox creates a list of language prefixes from both  and  .  Prefixes in   must match a language code in   to be added to the local list.  There are seven 'language-like' codes in   that 'redirect' to another-language wiki but these codes do not contribute to the inter-wiki language list:
 * → Mandarin Chinese (ISO 639-3 code); redirects to zh.wikipedia.org
 * → Czech (ISO 3166 country code); redirects to cs.wikipedia.org
 * → Danish (ISO 3166 country code); redirects to da.wikipedia.org
 * → Esperanto (ISO 639-3 code); redirects to eo.wikipedia.org
 * → Japanese (ISO 3166 country code); redirects to ja.wikipedia.org
 * → invalid IETF language tag; redirects to zh-min-nan.wikipedia.org
 * → invalid IETF language tag; redirects to zh-min-nan.wikipedia.org
 * These are not included in the local prefix list.
 * —Trappist the monk (talk) 15:56, 5 August 2020 (UTC)
 * Can't remember anymore where I saw it, but there's a case where one type of Norwegian language code—whether  (Norwegian, in general) or   (Nynorsk), I can't remember —is odd man out, wrt to a giant list of WP codes that generally match the ccTLD codes, except for that one case. (There's also Bokmal, , but it wasn't that.) This could be a red herring, but just wanted to recall it, in case it's relevant here. Mathglot (talk) 03:40, 6 August 2020 (UTC)
 * I'm not sure I understand what it is that you are saying.   links to the Norsk nynorsk nn.wiki, both of   and   link to the Norsk bokmål nb.wiki.  I do remember that for a time, language code   was not supported by the   magic word.  That has since been fixed:
 * —Trappist the monk (talk) 10:30, 6 August 2020 (UTC)
 * Found it, and it doesn't affect this issue, because it's about translation, not linking. If you're curious, it's used at Template:Expand Norwegian (Nynorsk); note the diff between langcode and googlelangcode, not found in any other Expand language template (such as Template:Expand Norwegian). The explanation at this /doc page references Nynorsk. So, red herring, as far as we are concerned here. Mathglot (talk) 04:28, 7 August 2020 (UTC)
 * → Danish (ISO 3166 country code); redirects to da.wikipedia.org
 * → Esperanto (ISO 639-3 code); redirects to eo.wikipedia.org
 * → Japanese (ISO 3166 country code); redirects to ja.wikipedia.org
 * → invalid IETF language tag; redirects to zh-min-nan.wikipedia.org
 * → invalid IETF language tag; redirects to zh-min-nan.wikipedia.org
 * These are not included in the local prefix list.
 * —Trappist the monk (talk) 15:56, 5 August 2020 (UTC)
 * Can't remember anymore where I saw it, but there's a case where one type of Norwegian language code—whether  (Norwegian, in general) or   (Nynorsk), I can't remember —is odd man out, wrt to a giant list of WP codes that generally match the ccTLD codes, except for that one case. (There's also Bokmal, , but it wasn't that.) This could be a red herring, but just wanted to recall it, in case it's relevant here. Mathglot (talk) 03:40, 6 August 2020 (UTC)
 * I'm not sure I understand what it is that you are saying.   links to the Norsk nynorsk nn.wiki, both of   and   link to the Norsk bokmål nb.wiki.  I do remember that for a time, language code   was not supported by the   magic word.  That has since been fixed:
 * —Trappist the monk (talk) 10:30, 6 August 2020 (UTC)
 * Found it, and it doesn't affect this issue, because it's about translation, not linking. If you're curious, it's used at Template:Expand Norwegian (Nynorsk); note the diff between langcode and googlelangcode, not found in any other Expand language template (such as Template:Expand Norwegian). The explanation at this /doc page references Nynorsk. So, red herring, as far as we are concerned here. Mathglot (talk) 04:28, 7 August 2020 (UTC)
 * —Trappist the monk (talk) 10:30, 6 August 2020 (UTC)
 * Found it, and it doesn't affect this issue, because it's about translation, not linking. If you're curious, it's used at Template:Expand Norwegian (Nynorsk); note the diff between langcode and googlelangcode, not found in any other Expand language template (such as Template:Expand Norwegian). The explanation at this /doc page references Nynorsk. So, red herring, as far as we are concerned here. Mathglot (talk) 04:28, 7 August 2020 (UTC)
 * Found it, and it doesn't affect this issue, because it's about translation, not linking. If you're curious, it's used at Template:Expand Norwegian (Nynorsk); note the diff between langcode and googlelangcode, not found in any other Expand language template (such as Template:Expand Norwegian). The explanation at this /doc page references Nynorsk. So, red herring, as far as we are concerned here. Mathglot (talk) 04:28, 7 August 2020 (UTC)

Also, while I'm thinking of it: despite the emission of a CS1 error in preview mode, the editor can still override and save anyway, as shown in your sandbox example above. This is fine, for the *-link case, but not so great for the publisher= Seuil case, because if that link is saved like that, the Wikidata bot will likely do something strange. I don't know if this is beyond the scope of this template, but, for example, could you stop the user from saving it in that form, either by stripping out the brackets, or supplying the preceding colon? If not, maybe in that case we'd need to see about an edit filter to trap it, but I suppose that would be a discussion for somewhere else. Mathglot (talk) 09:50, 5 August 2020 (UTC)
 * Hm, maybe not so fine in the *-link case, either; they can both lead to downstream problems of rendering and knock-on issues at Wikidata, if I'm not mistaken. Mathglot (talk) 03:47, 6 August 2020 (UTC)
 * Tweaks to the code:
 * For <param-link> parameters that fail the various link tests (has a url, has wikilink markup, has inter-wiki prefix without leading colon) the code simply unsets the parameter and declares the error:
 * For [[ <prefix>:<value>|undefined the code extracts the label portion of the wikilink:
 * These tweaks prevent the addition of extraneous inter-wiki links in the languages list.
 * That languages inter-wiki list at left must have a proper name. What is that name?
 * —Trappist the monk (talk) 13:31, 6 August 2020 (UTC)
 * Usually just inter-language list or inter-wiki list. The latter can be ambiguous since the introduction of the inter-project list. --Izno (talk) 14:33, 6 August 2020 (UTC)
 * I've always just called it the "language links sidebar" (or "language sidebar", on the second occasion) because I've never seen anyone misunderstand what that means, but I don't know if there's an official term.
 * Thanks so much for tweaks here and earlier; this is going to really improve things. I wonder how many "stealth errors" are out there—defining that as something that "seemed all right" until now, that suddenly will generate a CS1 error where it didn't before. Do we care? I imagine editors at the articles concerned will wonder why something turned red that never was before, but all they have to do is click the [help] to find out. This is great stuff, thanks Trappist. Mathglot (talk) 03:07, 7 August 2020 (UTC)
 * These tweaks prevent the addition of extraneous inter-wiki links in the languages list.
 * That languages inter-wiki list at left must have a proper name. What is that name?
 * —Trappist the monk (talk) 13:31, 6 August 2020 (UTC)
 * Usually just inter-language list or inter-wiki list. The latter can be ambiguous since the introduction of the inter-project list. --Izno (talk) 14:33, 6 August 2020 (UTC)
 * I've always just called it the "language links sidebar" (or "language sidebar", on the second occasion) because I've never seen anyone misunderstand what that means, but I don't know if there's an official term.
 * Thanks so much for tweaks here and earlier; this is going to really improve things. I wonder how many "stealth errors" are out there—defining that as something that "seemed all right" until now, that suddenly will generate a CS1 error where it didn't before. Do we care? I imagine editors at the articles concerned will wonder why something turned red that never was before, but all they have to do is click the [help] to find out. This is great stuff, thanks Trappist. Mathglot (talk) 03:07, 7 August 2020 (UTC)
 * Thanks so much for tweaks here and earlier; this is going to really improve things. I wonder how many "stealth errors" are out there—defining that as something that "seemed all right" until now, that suddenly will generate a CS1 error where it didn't before. Do we care? I imagine editors at the articles concerned will wonder why something turned red that never was before, but all they have to do is click the [help] to find out. This is great stuff, thanks Trappist. Mathglot (talk) 03:07, 7 August 2020 (UTC)

Template-specific help in preview
Hi, I guess most of us do not remember all parameters supported by the various citation templates, in particular those which are not generic, but specific to certain templates.

In order to make it easier (quicker) to look up the template specific help page, I propose to let the template display an unobtrusive link to its help page (only) in article preview, either in front of the citation or after it.

This could look like

Cite journal would have a link to Help:Cite journal, Cite conference to Help:Cite conference, Cite book to Help:Cite book etc.

If even this small [?] would be found to be too obtrusive, it could be put into some CSS stuff so that it would show only when an editor has opted in to maintenance messages.

--Matthiaspaul (talk) 11:01, 13 July 2020 (UTC)
 * I'm not sure I'd support that specific implementation, but the idea has merit and I'd support some variant of it. Possibly

As a preview/opt-in message.  Headbomb {t · c · p · b} 12:42, 13 July 2020 (UTC)
 * Whatever we can agree upon. I deliberately tried to make it as short and unobtrusive as possible to not change the general appearance in preview, but if people would prefer longer messages as in your example, I would not be against it, either. --Matthiaspaul (talk) 12:54, 13 July 2020 (UTC)
 * Perhaps something like this (image instead of text) would be aesthetically more pleasing?

 * --Matthiaspaul (talk) 15:54, 13 July 2020 (UTC)
 * Really should be at the end I feel, but YMMW. The real question is do we want this as default, or as an opt-in preview, or handled by a separate script?   Headbomb {t · c · p · b} 18:45, 13 July 2020 (UTC)

 * I definitely don’t think it should be the default. It’s confusing for editors to see things in the preview that don’t appear in the finished page, and question marks or comments like “need help?” suggest something is questionable or that editor needs help, implies something is wrong even when it’s formatted correctly. Umimmak (talk) 18:58, 13 July 2020 (UTC)
 * This seems like something that could be created as a javascript that would give the little icon or a link for all templates, not just CS1 templates. I see people having trouble with editing a wide variety of templates, putting in incorrect parameters and much more. – Jonesey95 (talk) 19:02, 13 July 2020 (UTC)
 * Nothing against a script-based solution, but unfortunately I personally couldn't take much advantage of it then as I usually have JavaScript disabled for security reasons...
 * --Matthiaspaul (talk) 20:55, 13 July 2020 (UTC)
 * I don't think this would cause much confusion, as it is self-explanatory. The curious user would click it once or twice to see what it is, and then take it for granted almost as if it would be a style element of the skin. I don't think the user needs a lengthly description in each citation, because once read its purpose is obvious. Some users might even miss the feature for some while, but that's the same with other interface elements - they will be stumbled upon and then used (if intuitive). That's why my preferred implementation would use a link as small as possible - ideally, I would even "reuse" some existing style element (like the "^"), but then it would have to be implemented as part of Mediawiki's token rather than inside our local citation templates (however, this won't work because only the citation template itself knows the location of its help page).
 * If a question mark would draw the wrong association, we could use something like a "book" or "file" icon to indicate "documentation" or even something more abstract like a (diagonally) upwards-pointing arrow (similar to the external-link icon, but pointing in one direction only) to indicate "look up".
 * --Matthiaspaul (talk) 20:55, 13 July 2020 (UTC)
 * The reason why I prefer the link in front of the citation (at least when it remains as short as in my example) is because it then "blends in" visually with the other "strange" symbols (like the "1./2.", "^" typically found in front of citations), whereas at the end of a citation there is often other text following (inside the

 * Not too bad, I would think...
 * --Matthiaspaul (talk) 16:20, 19 July 2020 (UTC)
 * Nice coincidence, when one clicks on "View history" on a page, a circled black question mark icon appears in the upper right corner leading to Help:Page history. So, there is even some precedent for this... ;-)
 * --Matthiaspaul (talk) 20:58, 19 July 2020 (UTC)

 * cs1|2 renders differently in preview mode only when there are archive-url errors. The initial implementation of that queried the   magic word for every citation whether there were errors or not.  That implementation drew the attention of MediaWiki because it took longer to save pages.  This because preview-pages are different from saved pages so MediaWiki can't reuse the preview and must parse the wikitext again before it can be saved.  See  and the related discussion at.
 * —Trappist the monk (talk) 19:17, 13 July 2020 (UTC)

 * Obviously, I would have used as well to detect preview mode... Let's loop in User:Aaron Schulz to see if there is meanwhile another way to detect preview - after all, four years have passed...
 * Is there a CSS class for "preview messages", that is, something that is visible only in preview without being conditional on ?
 * --Matthiaspaul (talk) 02:22, 14 July 2020 (UTC)

 * A bit too much insider jargon for me to decipher if the issue has been worked around by User:Aaron Schulz in 2019, so I'll drop these finds here for evaluation and comment by those who are familiar with the implementation:
 * https://gerrit.wikimedia.org/r/c/mediawiki/core/+/294774/ 2019-04-02 "Disable expensive magic word in miser mode"
 * https://phabricator.wikimedia.org/T137900 "Deal with poor edit stash hit rate due to Lua modules using "
 * https://gerrit.wikimedia.org/r/c/mediawiki/core/+/503685/ 2019-04-15 "parser: use "-" for revision ID for non-preview edit filter parse during save"
 * https://phabricator.wikimedia.org/T235957 2019-10-19 "Change from number to "-" in wgMiserMode"
 * https://gerrit.wikimedia.org/r/c/mediawiki/core/+/570985/ 2020-02-18 "parser: apply $wgMiserMode restriction to REVISIONID for NS_USER/NS_PROJECT"
 * --Matthiaspaul (talk) 17:26, 15 July 2020 (UTC)
 * On 2019-04-04, User:Krinkle wrote :
 * "The magic word is being deprecated for performance reasons. In the future, it will only return "" (empty string) when previewing edits, or "-" (dash) when reading pages. The release of next week, will only change this behaviour for articles in the content namespaces. It will not change for interface messages and other namespaces (such as talk pages, and user pages)."
 * So, it basically has reduced to a flag now.
 * Anyway, I would prefer to see such help links in preview rather than saving a few seconds on save. Comments?
 * --Matthiaspaul (talk) 15:49, 18 July 2020 (UTC)
 * Having reread the other threads, I have come to the conclusion that we can assume the issue as being worked around at least to an extent that using does no longer cause a significant performance hit that could not be remedied on server side.
 * On 2016-06-22, User:Ori Livneh/User:ATDT wrote (Help talk:Citation Style 1/Archive 20):
 * We try to do all the work except actually save the edit to the database. If the user does not end up saving the edit or if the user goes back and makes additional changes, we just throw away whatever we computed. But if the user saves the edit, then often times a lot of the work is already done and all we have to do is commit it to the database. Whenever the REVISIONID magic word is used, this whole mechanism is basically subverted, because we can't reliable know in advance what the revision ID is going to be before we save it to the database.
 * However, with reduced to something like a  flag, the pseudo-revision ID can be predicted (even during preview) to be "-" when later saving a page, thus the precompiled page can be reused with no or only minor fixups. What still might differ is the resulting HTML (with or without the help icons), but nobody would keep them from silently generating the HTML for the "-" case during preview already (in addition to the preview itself), so, while this may still require two passes, there is no need to defer the final pass until the user hits "Save", thus no performance penalty on the user side.
 * In the worst case, the feature could be made conditional on citation errors occuring. In this case, it would not show for all citations in preview but at least for those where errors were detected and thus help is particulary useful.
 * --Matthiaspaul (talk) 18:06, 19 July 2020 (UTC)
 * Apparently, none of the three pinged server admins/developers can be bothered to reply. Since the problem apparently no longer exists, let's go for it. --Matthiaspaul (talk) 12:35, 8 August 2020 (UTC)

Why does Wikiquote's Ref template and Wikipedia's Ref template handle commas in the date field differently?
(X-posting from the Tech Pump) Wikiquote's ref template will parse "July 2 1999" just fine, but our template requires a comma, e.g. "July 2, 1999". Why is that? Can someone fix our template to stop caring so much? I screw this up on my first pass something like 25% of the time. -- Kendrick7talk 00:30, 7 August 2020 (UTC)
 * "July 2 1999" is not a valid date format here on the English Wikipedia, per MOS:DATESNO, so our CS1 citation templates (e.g. cite web and similar) display an error message. Wikiquote does not have enforceable date styles (per the English Wikiquote MOS), so ambiguous and non-standard dates aren't marked as errors. – Jonesey95 (talk) 01:58, 7 August 2020 (UTC)
 * What does MOS have to do with it? Wikiquote's template simply inserts the comma automatically, so the styling result is exactly the same. -- Kendrick7talk 12:37, 7 August 2020 (UTC)
 * Which template is doing this formatting? See my wikiquote sandbox, where Template:cite news on wikiquote is leaving "July 2 1999" alone. You are welcome to add examples to that sandbox page. – Jonesey95 (talk) 15:43, 7 August 2020 (UTC)
 * Wikiquote's version of "cite web" is definitely adding the comma; I've added an example to your sandbox. I don't know why I expected consistency, lol. -- Kendrick7talk 00:22, 8 August 2020 (UTC)

Some maintenance items to upgrade to errors
Right now, Category:CS1 maint: display-authors and other friends are nearly always empty because they are nearly always an easy-to-correct error. I would like to propose upgrading them to errors accordingly, which will make them more visible to editors.

To make this easier to do in the future with maintenance messages we decide should be errors, I'd also like to see the error and maintenance system implementations be made the same (save for the obvious distinction). For this latter, I trip up really hard every time I want to get maintenance items turned into errors, and it's making it hard to parse how to make the necessary code modification for display-X.

Any concerns? --Izno (talk) 12:45, 4 July 2020 (UTC)
 * After the next update which I am about to announce.
 * Error messages rely on tables defined in Module:Citation/CS1/Configuration. Each error message has four properties: ,  ,  ,  .  For maint cats, we might define these:
 * always  or empty string
 * a unique value used to link into Help:CS1 errors help text
 * the key that tells common  how to handle the issue; maint cat names all begin with 'CS1 maint:' whereas error message cats aren't so consistent
 * ignored for maint cats which are always hidden
 * is presently a member of but doesn't necessarily belong there.  In Module:Citation/CS1/Identifiers this cat and its dependents are treated as pseudo errors (the categories are created and added to the table  .  Property and maint cats have their own tables (  and  ).  Maint cats can display their names as an editor-option via css, prop cats display nothing.
 * Before we embark on a messaging rewrite, we should normalize, somehow, the inactive doi handling. Inactive dois are not errors in the sense of cs1 errors like any of the categorized errors in .  Neither are they simple properties because they should be fixed.  We could treat inactive dois as maint issues so that editors who have turned on maint messaging can see locate the inactive dois.
 * Another thing that I would like to do is standardize the location of error messages. We have a mix of locations: some error messages are adjacent to where the element occurs in the rendered citation and the other are all listed at the end.  I have a preference for grouping all of the error messages at the end.  Maint messaging is all rendered at the end of the citation.
 * Assuming that we do all of this, the simple case conversion from maint message to error message is to change  to the correct error cat; add the appropriate error message in , and set   to the appropriate boolean.
 * No doubt, this enumeration is incomplete ...
 * —Trappist the monk (talk) 15:30, 4 July 2020 (UTC)
 * Speaking of error messages, it might be worthwhile to also improve the preview messages on duplicated parameters so that they provide some location information. In articles with many citations it sometimes takes quite a while to spot the citation using e.g. date twice. --Matthiaspaul (talk) 07:58, 7 July 2020 (UTC)
 * That's a MediaWiki feature, unrelated to the citation templates. But there's a script, User:Frietjes/findargdups, which can tell you which template call has the duplicate. -- John of Reading (talk) 08:42, 7 July 2020 (UTC)
 * Thanks, John. --Matthiaspaul (talk) 14:27, 7 July 2020 (UTC)
 * The error message function has been renamed  →   and been modified so that it will emit maintenance category 'messages' when the   property for that message is  .  Maint messaging is now part of the   table in Module:Citation/CS1/Configuration/sandbox; TODO: rename that table.
 * Module talk:Citation/CS1/testcases2
 * —Trappist the monk (talk) 14:37, 30 July 2020 (UTC)
 * That's a MediaWiki feature, unrelated to the citation templates. But there's a script, User:Frietjes/findargdups, which can tell you which template call has the duplicate. -- John of Reading (talk) 08:42, 7 July 2020 (UTC)
 * Thanks, John. --Matthiaspaul (talk) 14:27, 7 July 2020 (UTC)
 * The error message function has been renamed  →   and been modified so that it will emit maintenance category 'messages' when the   property for that message is  .  Maint messaging is now part of the   table in Module:Citation/CS1/Configuration/sandbox; TODO: rename that table.
 * Module talk:Citation/CS1/testcases2
 * —Trappist the monk (talk) 14:37, 30 July 2020 (UTC)
 * —Trappist the monk (talk) 14:37, 30 July 2020 (UTC)

I worked my originating request as a result of this rework, which moves display_names messaging (inconsistently error and maintenance) to strictly errors. Main, /Configuration and testcases2. Perhaps of note that this changes the error for the "don't know" case from invalid_param_values to disp_name; I made that change to centralize all the disp_name errors fixing. There may be further work that should be done so the other use of that error can be more definite. --Izno (talk) 22:50, 8 August 2020 (UTC)

One other thing: I am not personally convinced that we need 5 categories to handle display_names issues. I think 1 would suffice. Seeking feedback on that point. --Izno (talk) 22:52, 8 August 2020 (UTC)

Template:Cite book needs additional terms
"Template:Cite Book" needs terms for all of the MARC 21 fields, especially total pages, size, etc.<IP_ADDRESS> (talk) 06:47, 24 July 2020 (UTC)
 * Why? The fields you mention are intended for cataloguing books. We are citing them, not cataloguing them. This information does not usually go into citations according to most commonly-used academic citation standards. Making fields for this information will just encourage people to fill them in under circumstances where they would be better off omitted. —David Eppstein (talk) 06:51, 24 July 2020 (UTC)
 * Agreed. It's actually confusing and detrimental to citations to add claptrap like this, especially total page count, since it's often mistaken for the pages being cited for the information the citation pertains to.  And we just have utterly no use for something like "quarto".  Yeesh.  Wikipedia is not anything like WorldCat.  — SMcCandlish ☏ ¢ 😼  13:00, 4 August 2020 (UTC)
 * "References" are not just citations. A "citation" only needs to identify a known reference; we need to describe the reference, for readers not able to just go over to a shelf and pick it up, and to convince the reader that it is in fact a valid reference for the subject of the article. Thus the academic standard does not apply; whether something is published as manuscript, paperback or hardcover does matter. Should there be a different template, "identify book" instead of "cite book"?<IP_ADDRESS> (talk)  —Preceding undated comment added 06:11, 7 August 2020 (UTC)

Fulltext access fields
I'm sure the way in which access is indicated in citations has been discussed extensively by the regulars here, and I apologize for my ignorance of your past discussions. Is there a field to indicate that a book is public-domain (in this case, a 2018 work of US government) and the fulltext is freely available online? This will make it obvious that it is easy to verify the cited statement, and increase the likelihood of editors and readers actually doing it. I understand that such access parameters are already common on journal article templates.

An additional winkle here: many medical journal articles are currently freely accessible due to a special action taken by publishers for the COVID-19 pandemic. At some future date to be decided upon by the publishers, they will put the articles back behind paywalls. Public licenses are permanent, but free access may be revoked. I'm not sure how widespread this is, but we might end up with a lot of incorrect information on access. HLHJ (talk) 17:29, 8 August 2020 (UTC)
 * Does answer your question?
 * —Trappist the monk (talk) 17:36, 8 August 2020 (UTC)

Help
I have a question about a book that is divided into several individual sections with their own authors. ¿How should I cite that book? In my case I am only interested in one section of that book. --Muwatallis II (talk) 23:11, 8 August 2020 (UTC)

 * is the basic skeleton. If you have some more information we can fill out the rest for you. --Izno (talk) 23:12, 8 August 2020 (UTC)

The book is called: Escuadra Nacional 1818-2018 (no author, only publisher)

The title of the chapter or section of the book already mentioned is: De la Guerra del Pacífico hasta fines del siglo XIX. The author is: Piero Castagneto Garviso. This author is just from the chapter or section of the book.

As I mentioned before, the book has other chapters or sections with their own authors, but I'm only interested in the one already mentioned. --Muwatallis II (talk) 00:04, 9 August 2020 (UTC)

 * is how that is done indeed. I expect there is an editor too who you might want to include, and of course a year. --Izno (talk) 00:25, 9 August 2020 (UTC)
 * +http://anyflip.com/yccc/bhap:
 * —Trappist the monk (talk) 00:30, 9 August 2020 (UTC)
 * —Trappist the monk (talk) 00:30, 9 August 2020 (UTC)

Placement of language annotation
When the source being cited is a chapter in an edited book or an article in a journal, the language of the source (specified with language) should be notated after the chapter or article, rather than after the book or journal, which may include items in several languages. For example, currently we have: The first is fine, but in the last two "(in German)" should be moved forward, after the chapter or article. Kanguole 11:50, 9 August 2020 (UTC)
 * Recently discussed here; see particularly my comments. --Izno (talk) 11:59, 9 August 2020 (UTC)
 * It seems there was substantial support for putting the annotation after the title of the item, with a few in favour of putting it at the end. Either would be better that the current practice of placing it after the name of the book, journal or series, which may be in several languages. But then the discussion got derailed onto formatting of multiple parentheticals. Kanguole 14:12, 9 August 2020 (UTC)
 * The conclusion you should draw is that the problem is not easy because of the paranetheticals. --Izno (talk) 14:47, 9 August 2020 (UTC)
 * Yeah, Kanguole summed it up well. While I have a preferences for moving it at the end (to avoid creating new problems), moving it after the most-specific title would have my support as well (but the parenthetical issues this creates would need more investigation IMO - some of them seem to be acceptable, whereas others just look too distracting to me - would be like trading one shortcoming for another).
 * --Matthiaspaul (talk) 16:19, 9 August 2020 (UTC)

trans-title= splits PDF format indication
In the following example, the "(PDF)" format designation comes after the translated title, which looks odd because the PDF symbol is displayed after the foreign language title:

There are several potential ways to solve this: Ideas? --Matthiaspaul (talk) 14:28, 20 June 2020 (UTC)
 * 1) Include the translation in the link - undesirable because the translation does not actually belong into there.
 * 2) Move the (format) designator in front of the translation - undesirable because it looks out of place there
 * 3) Move the PDF symbol after the translation - undesirable because it also serves as "external link" indicator, also not sure if this is technically possible
 * 4) Suppress the PDF symbol and replace it by the normal "external link" symbol. Do we really need the PDF symbol, anyway? (Do we support any other file types with special symbols?)

 * #4 is possible. Yes, other file types do have special symbols if the URL is a certain way and file type. PDF is understandably the most common. Because I have the link handy for Modern skin, the stylings applied to the others are in main.css. The other skins have similar rules, if not exactly the same. (See also phab:T225430.)
 * #3 is technically possibly. It would require including the trans-title in the link. (See also prior discussion.) If we do not want a sea of blue on this route, that is also technically possible but it would require an inaccessible design choice (to wit, making the link for some part of the title + trans-title not blue).
 * I would favor #2 if there is a consensus that this needs to change. It's puzzling that you think this undesirable given our recent discussions on parentheses stacking... ;) --Izno (talk) 14:59, 20 June 2020 (UTC)
 * Thanks for the links, Izno.
 * Well, I don't like #2, because it separates the actual title and the translation too much. To me, they belong together logically and therefore should not be separated - just like the format symbol and "(format)" text should be displayed in one location. To me, title information is far more important than format information, therefore, format information should not be inserted in the middle of title information, and in particular not given in two places.
 * Therefore, of the given choices, I would prefer #1 (which implies #3), that is, back to the old 2017 behaviour. Although I am not particularly fond of the potentially resulting long blue link labels, they would be of only minor concern to me (display cosmetics) - at least, they are logical.
 * For completeness, another solution would be to swap title and trans-title, but I don't actually suggest this, because I think the actual title should be displayed before the translation.
 * --Matthiaspaul (talk) 16:21, 20 June 2020 (UTC)
 * @Matthiaspaul: I've corrected the citation formatting above (but not in a way that affects the topic of this discussion). I hope you don't mind. Glades12 (talk) 07:03, 13 July 2020 (UTC)
 * Good to know that we meanwhile support script-* and trans-* parameter variants for them. I've changed it to magazine, though - they describe themselves as a magazine rather than as a journal. work is too unspecific. I use work only when none of the more descriptive parameters applies (typically with cite web or cite book, rarely with cite journal or cite magazine). --Matthiaspaul (talk) 10:22, 13 July 2020 (UTC)
 * There would be yet another way how this could be solved: Given that providing the PDF icon and a "(PDF)" text is redundant, we could simply suppress the "(format)" text if it resembles one of the external link types recognized and indicated by specific icons. If format is used to specify something different, it would be displayed as before, but then the icon and the text would not be redundant and therefore look much less out of place than now. --Matthiaspaul (talk) 18:12, 20 July 2020 (UTC)
 * It is not a given that the PDF icon and a "(PDF)" text is redundant. The pdf icon is rendered by MediaWiki as a css   property (MediaWiki:Common.css).  Because it is not rendered from an html  tag, it does not support the   attribute.  In cs1|2, the automatic PDF is a way to notify screen-reader-users that the source is a pdf file.  That functionality should not be degraded.
 * —Trappist the monk (talk) 18:56, 20 July 2020 (UTC)
 * I agree, accessibility is important. Still, there are potential remedies for this as well:
 * Instead of completely muting the "(format)" text when it would be redundant because of the icon, the text could then be made invisible to normal users, but left readable for screen-readers only:
 * https://webaim.org/techniques/css/invisiblecontent/
 * https://webaim.org/techniques/alttext/#background
 * Or, the global link decoration could be disabled and the PDF icon be displayed locally (as image, and with  text).
 * --Matthiaspaul (talk) 22:57, 20 July 2020 (UTC)
 * Well, I proposed various ways how to possibly solve this. If they are undesirable, I think, per Izno's offer in the old discussion we should switch back to the 2017 behaviour (basically item #1 in the list). It might be a bit blueish at times, but at least it is logical.
 * --Matthiaspaul (talk) 11:32, 10 August 2020 (UTC)
 * I was referring you to the discussion where in fact I implemented the newer behavior. I am not interested in returning to the old behavior solely for this concern, and given the general lack of feedback, I'm not sure anyone sees this as a strong concern at this time. --Izno (talk) 20:40, 10 August 2020 (UTC)

How to disable the link?
There's a few links I've seen in references to old webpages with valid archive URLs of what the site looked like in 1997, but there's malware-downloading squatters at the URL now. Is there a way to suspend a link to the site in this template? Or should the URL just be replaced directly with the archive link in such cases? SnowFire (talk) 05:53, 10 August 2020 (UTC)
 * If you add  to the citation, the original URL will not be linked. Read more at Template:Cite web/doc. -- John of Reading (talk) 06:07, 10 August 2020 (UTC)

source: wikimedia

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Help talk:Citation Style 1/Archive 69


text:
War Emblem

War Emblem (February 20, 1999 – March 11, 2020) was a champion American Thoroughbred racehorse who won the 2002 Kentucky Derby and Preakness Stakes.

Background
War Emblem was bred by Charles Nuckols Jr. & Sons in Kentucky. His sire was Our Emblem, a stakes placed son of leading sire Mr. Prospector and the undefeated mare Personal Ensign. War Emblem's dam was Sweetest Lady by Lord At War. Often described as nearly black, he was registered as dark bay or brown colt with a white star. In the 2000 Keeneland September Yearling Sale, he failed to meet his reserve of $20,000 so raced under the colors of Russell Reineman, who had owned the colt's dam. Initially, he was trained by Frank Springer.

Described as narcissistic, War Emblem was a temperamental horse who did not like people nor other horses: Bob Baffert nicknamed the colt 'Hannibal Lecter' for his habit of biting. He had a history of bone chips in his knees and ankles, which discouraged several potential buyers. He liked to race at the front of the field, but sometimes compromised his own chances by acting up in the starting gate.

Racing career
As a two-year-old, War Emblem won his first start, but then finished seventh when entered in the Manila Stakes. He rebounded with a win in an allowance race to finish 2001 with a record of two wins from three starts.

His three-year-old campaign started poorly, with a fifth place in the Lecomte Stakes and a sixth-place finish in the Risen Star, both at Fair Grounds Race Course. He returned to form with a $10 3/4$ length win in an allowance race at Sportsman's Park Racetrack, then won the Illinois Derby by $6 1/4$ lengths in wire-to-wire fashion. Prince Ahmed bin Salman of Saudi Arabia bought a ninety percent interest in War Emblem for a reported $1 million just three weeks before the Kentucky Derby.

Victor Espinoza was his jockey for the 2002 Kentucky Derby, never having seen the horse until the morning of the race. War Emblem, who went off at 21-to-1 odds, took the early lead and sent sensible early fractions, then kicked away from the field in the stretch. He won the race in a fast time of 2:01.13. It was the first Kentucky Derby win for new owner Salman and the third for new trainer Bob Baffert. War Emblem beat the likes of Medaglia d'Oro (winner of the Travers Stakes, Jim Dandy Stakes, and Whitney Handicap, among others); Perfect Drift (winner of the Stephen Foster, the Indiana Derby, and the Washington Park Handicap twice, among others); and Harlan's Holiday (winner of the Florida Derby, the Pennsylvania Derby, and the Donn Handicap among others).

In the 2002 Preakness Stakes, War Emblem rated just behind the leaders who set a fast pace, went to the lead on the far turn and held off a late rally by Magic Weisner. With a Triple Crown at stake, the Belmont Stakes on June 8 attracted the biggest crowd in the track's history with 103,222 spectators. War Emblem stumbled and nearly fell to his knees coming out of the gate, then bumped into another horse, losing several lengths in the process. He then struggled with Espinoza who tried to rate the colt down the backstretch. War Emblem surged to the lead in the final turn before fading at the top of the stretch: The winner was 70-1 long-shot Sarava. It was the third time Baffert had lost the Belmont with a Triple Crown at stake: He had previously lost with Silver Charm in 1997 and Real Quiet in 1998. Baffert later said, "He was so one-dimensional and such an irritable horse as it was, as soon as he was behind horses, I had to sit there for 2½ minutes waiting for the race to be over."

War Emblem returned to the track on August 4 as the favorite in the Haskell Invitational Handicap and won easily by $3 1/2$ lengths. Baffert said, "You forget how good this horse is. From now on we're just going to let him run the way he wants. If he were one of those wild horses in the herd, he'd be the top dog. Like 'The Black Stallion', you don't want to break that spirit." He became the first horse to win the Kentucky Derby and Haskell.

War Emblem then traveled to California for the Pacific Classic on August 25 at Del Mar against older horses. He broke poorly but quickly settled into second place and seemed to be running well. However, he tired coming into the stretch and finished sixth. In his final start at Arlington Park on October 26, he finished eighth in the Breeders' Cup Classic. War Emblem finished his career with seven wins from 13 starts and earnings of $3,491,000. In his six losses, he finished no better than fifth. He received the Eclipse Award for champion three-year-old colt of 2002 and was a distant runner-up to Azeri in the Horse of the Year voting.

Career as a sire
In September 2002, War Emblem was sold to the prominent Yoshida racing family of Japan for US$17.7 million to stand at stud at their renowned Shadai Stallion Station in Shiraoi, Hokkaido.

Expected to follow in the footsteps of Shadai's great sires Northern Taste and Sunday Silence, War Emblem did not fulfill those expectations in the breeding shed. "We know he is fertile, but he has no interest in mares", said Dr. Nubuo Tsunoda, the farm's director. For his first year at stud in 2003, only four foals were produced in 2004. His second year was more successful, resulting in nineteen colts and fifteen fillies born in 2005. However, his third crop born in 2006 consisted of only four colts and one filly. In the next two years, War Emblem rejected nearly every mare presented to him so no foals were produced in 2007 and 2008. On June 8, 2008, War Emblem was evaluated by a stallion behavior team from the University of Pennsylvania. They suggested that he should be separated from other stallions to help improve his breeding behavior. The measures seemed to help War Emblem in the 2009 breeding season, with a career record of 43 foals born in 2010. However, War Emblem reverted to his old habits in 2010, only covering five of 300 mares presented to him in the season. In 2012, he covered only three mares, none of whom became pregnant. In total, he sired only 106 registered foals between 2004 and 2011.

Although War Emblem only sired a total of 119 foals, his progeny proved quite successful on a percentage basis, with 80 winners from 111 starters and combined progeny earnings of $35,300,307. His last foal was born in 2012. He was represented by his first career stakes winner in 2008 when Shonan Alba (Xianlang (IRE), by Great Commotion) won the Kyodo News Service Hai, an 1,800 meter listed race on Tokyo Race Course's turf course. Nearly a month later, the filly Air Pascale (Raffica, by Sunday Silence) scored in the listed Tulip Sho at Hashin Race Course. On March 22, another filly, Black Emblem (Vin de Noir, by Hector Protector), became War Emblem's first classic winner with an odds-on victory in the Shuka Sho, the final leg of the Japanese Fillies' Triple Crown. Black Emblem later became dam of two stakes winners, Bright Emblem and Testament. War Emblem's most successful offspring was Robe Tissage, who was the champion two-year-old filly in Japan in 2012. He also sired Group 3 winners King's Emblem and War Tactics, and stakes winners Civil War, Danon Programmer, and Clan Emblem.

His son, Civil War, was sent to stud. Due to initial fears he would exhibit his sire's habits in the breeding shed, a special "conception confirmation"-clause was issued. At first year, Civil War covered 62 mares.

Retirement and death
In Fall of 2015,War Emblem was pensioned from stallion duty and repatriated to the United States, where he was sent to live at Old Friends Equine Retirement in Georgetown, Kentucky. Although he was not going to be used at stud, USDA regulations required that all stallions imported to the U.S. be tested for contagious equine metritis via test-breeding two mares. After a month in quarantine at the Rood & Riddle Equine Hospital, War Emblem declined breeding with any mares presented to him, and in order to keep him in the United States, the only remaining option was to geld him. The operation was a success with a full recovery by War Emblem at the age of 17 in 2016. War Emblem was found dead in his paddock at Old Friends Equine on March 11, 2020, at the age of 21. The cause of death was later found to be a ruptured small intestine.

title: War Emblem


text:
Fort Montagne à la Bosse

Fort Montagne à la Bosse (literally "Hump Mountain") was a North West Company trading post from 1790 until 1805 or after during the Assiniboine River fur trade.

It was located near Virden, Manitoba on the Assiniboine River at the point where the river bends from southeast to east. At some point it was closed and reopened in 1794. It was on the prairie and produced buffalo and wolf skins more than beaver, but its primary product was pemmican to feed the voyageurs further north. At one time it and Fort Esperance produced the bulk to the NWC's buffalo meat. As the southwesternmost post it had some contact with the Mandans in North Dakota, but the main Mandan trade was from Brandon House. During the Lewis and Clark Expedition there was an exchange of messages with the explorers at Fort Mandan and Fort Montagne à la Bosse. In 1805 François-Antoine Larocque left here on his journey to the Yellowstone River.

It was in a stockade of 200 by 250 feet on a high bank that overlooked the surrounding plain. The location is marked by a cairn near 49.8392°N, -100.84425°W about 2.5 miles east of Virden. The original site was destroyed by gravel extraction either for the Canadian Pacific Railway or for the old Highway No 1. Peter Grant had an ill-documented post nearby.

title: Fort Montagne à la Bosse


text:
Introduction to Paleoanthropology/Acheulean

In 1866, German biologist Ernst Haeckel had proposed the generic name "Pithecanthropus" for a hypothetical missing link between apes and humans.

In late 19th century, Dutch anatomist Eugene Dubois was on the Indonesian island of Java, searching for human fossils. In the fall of 1891, he encountered the now famous Trinil skull cap. The following year his crew uncovered a femur, a left thigh bone, very similar to that of modern humans. He was convinced he had discovered an erect, apelike transitional form between apes and humans. In 1894, he decided to call his fossil species Pithecanthropus erectus. Dubois found no additional human fossils and he returned to the Netherlands in 1895.

Others explored the same deposits on the island of Java, but new human remains appeared only between 1931 and 1933.

Dubois's claim for a primitive human species was further reinforced by nearly simultaneous discoveries from near Beijing, China (at the site of Zhoukoudian). Between 1921 and 1937, various scholars undertook fieldwork in one collapsed cave (Locality 1) recovered many fragments of mandibles and skulls. One of them, Davidson Black, a Canadian anatomist, created a new genus and species for these fossils: Sinanthropus pekinensis ("Peking Chinese man").

In 1939, after comparison of the fossils in China and Java, some scholars concluded that they were extremely similar. They even proposed that Pithecanthropus and Sinanthropus were only subspecies of a single species, Homo erectus, though they continued to use the original generic names as labels.

From 1950 to 1964, various influential authorities in paleoanthropology agreed that Pithecanthropus and Sinanthropus were too similar to be placed in two different genera; and, by the late 1960s, the concept of Homo erectus was widely accepted.

To the East Asian inventory of H. erectus, many authorities would add European and especially African specimens that resembled the Asian fossil forms. In 1976, a team led by Richard Leakey discovered around Lake Turkana (Kenya) an amazingly well-preserved and complete skeleton of a H. erectus boy, called the Turkana Boy (WT-15000).

In 1980s and 1990s:
 * new discoveries in Asia (Longgupo, Dmanisi, etc.); in Europe (Atapuerca, Orce, Ceprano);
 * precision in chronology and evolution of H. erectus;
 * understanding and definition of variability of this species and relationship with other contemporary species.

Africa
Unlike Australopithecines and even Homo habilis, Homo ergaster/erectus was distributed throughout Africa:
 * about 1.5 million years ago, shortly after the emergence of H. ergaster, people more intensively occupied the Eastern Rift Valley;
 * by 1 million years ago, they had extended their range to the far northern and southern margins of Africa.

Traditionally, Homo erectus has been credited as being the prehistoric pioneer, a species that left Africa about 1 million years ago and began to disperse throughout Eurasia. But several important discoveries in the 1990s have reopened the question of when our ancestors first journeyed from Africa to other parts of the globe. Recent evidence now indicates that emigrant erectus made a much earlier departure from Africa.

Israel
Ubeidiyeh
 * Deposits accumulated between 1.4-1.0 million years ago;
 * Stone tools of both an early chopper-core (or Developed Oldowan) industry and crude Acheulean-like handaxes. The artifacts closely resemble contemporaneous pieces from Upper Bed II at Olduvai Gorge;
 * Rare hominid remains attributed to Homo erectus;
 * Ubeidiya might reflect a slight ecological enlargement of Africa more than a true human dispersal.

Gesher Benot Yaaqov
 * 800,000 years ago;
 * No hominid remains;
 * Stone tools are of Acheulean tradition and strongly resemble East African industries.

Republic of Georgia
In 1991, archaeologists excavating a grain-storage pit in the medieval town of Dmanisi uncovered the lower jaw of an adult erectus, along with animal bones and Oldowan stone tools.

Different dating techniques (paleomagnetism, potassium-argon) gave a date of 1.8 million years ago, that clearly antedate that of Ubeidiya. Also the evidence from Dmanisi suggests now a true migration from Africa.

China
Longgupo Cave
 * Dated to 1.8 million years ago
 * Fragments of a lower jaw belonging either to Homo erectus or an unspecified early Homo.
 * Fossils recovered with Oldowan tools.

Zhoukoudian
 * Dated between 500,000 and 250,000 years ago.
 * Remarkable site for providing large numbers of fossils, tools and other artifacts.
 * Fossils of Homo erectus discovered in 1920s and 1930s.

Java
In 1994, report of new dates from sites of Modjokerto and Sangiran where H. erectus had been found in 1891.

Geological age for these hominid remains had been estimated at about 1 million years old. Recent redating of these materials gave dates of 1.8 million years ago for the Modjokerto site and 1.6 million years ago for the Sangiran site.

These dates remained striking due to the absence of any other firm evidence for early humans in East Asia prior to 1 Myrs ago. Yet the individuals from Modjokerto and Sangiran would have certainly traveled through this part of Asia to reach Java.

Europe
Did Homo ergaster/erectus only head east into Asia, altogether bypassing Europe?

Many paleoanthropologists believed until recently that no early humans entered Europe until 500,000 years ago. But the discovery of new fossils from Spain (Atapuerca, Orce) and Italy (Ceprano) secured a more ancient arrival for early humans in Europe.

At Atapuerca, hundreds of flaked stones and roughly eighty human bone fragments were collected from sediments that antedate 780,000 years ago, and an age of about 800,000 years ago is the current best estimate. The artifacts comprise crudely flaked pebbles and simple flakes. The hominid fossils - teeth, jaws, skull fragments - come from several individuals of a new species named Homo antecessor. These craniofacial fragments are striking for derived features that differentiate them from Homo ergaster/erectus, but do not ally them specially with either H. neanderthalensis or H. sapiens.


text:
User:Kizer/Web Page/Fireworks/Effects

1.	Once you have fireworks open, click file new and create your image or type what you want on the canvas

2.	Click the black curser on the left side toolbar and click the image you want to have a shadow or glow.

3.	Once clicked look on the bottom right of the screen and you should see a button that says effects and has a + sign, click on it

4.	Once clicked you should see a menu pop up, once up click shadow and glow and choose your desired effect

5.	After you click your wanted effect, another menu should pop up and that is where you can fine tune you effect and customize it.

6.	Once done customizing click back on the screen to get rid of the menu and there should be your new and improved graphic.

7.	If you desire to remove the effect simply click in the effect box where it displays your effects and click the word your effect was and then click the - symbol next to the + symbol and your effect should disappear

SpicerK 18:18, 19 January 2007 (UTC)

title: User:Kizer/Web Page/Fireworks/Effects


text:
Green marketing

Green marketing is the marketing of products that are presumed to be environmentally safe. It incorporates a broad range of activities, including product modification, changes to the production process, sustainable packaging, as well as modifying advertising. Yet defining green marketing is not a simple task. Other similar terms used are environmental marketing and ecological marketing.

Green, environmental and eco-marketing are part of the new marketing approaches which do not just refocus, adjust or enhance existing marketing thinking and practice, but also seek to challenge those approaches and provide a substantially different perspective. In more detail green, environmental and eco-marketing belong to the group of approaches which seek to address the lack of fit between marketing as it is currently practiced and the ecological and social realities of the wider marketing environment.

The legal implications of marketing claims call for caution or overstated claims can lead to regulatory or civil challenges. In the United States, the Federal Trade Commission provides some guidance on environmental marketing claims. The commission is expected to do an overall review of this guidance, and the legal standards it contains, in 2011.

History
The term Green Marketing came into prominence in the late 1980s and early 1990s. The American Marketing Association (AMA) held the first workshop on “Ecological Marketing” in 1975. The proceedings of this workshop resulted in one of the first books on green marketing entitled "Ecological Marketing".

The Corporate Social Responsibility (CSR) Reports started with the ice cream seller Ben & Jerry's where the financial report was supplemented by a greater view on the company's environmental impact. In 1987 a document prepared by the World Commission on Environment and Development defined sustainable development as meeting “the needs of the present without compromising the ability of future generations to meet their own need”, this became known as the Brundtland Report and was another step towards widespread thinking on sustainability in everyday activity. Two tangible milestones for the first wave of green marketing came in the form of published books: Green Marketing by Ken Peattie (1992) in the United Kingdom and Green Marketing: Challenges & Opportunities for the New Marketing Age by Jacquelyn Ottman (1993) in the United States of America.

According to Jacquelyn Ottman, (author of "The New Rules of Green Marketing: Strategies, Tools, and Inspiration for Sustainable Branding" (Greenleaf Publishing and Berrett-Koehler Publishers, February 2011)) from an organizational standpoint, environmental considerations should be integrated into all aspects of marketing — new product development and communications and all points in between. The holistic nature of green also suggests that besides suppliers and retailers new stakeholders be enlisted, including educators, members of the community, regulators, and NGOs. Environmental issues should be balanced with primary customer needs.

The "Green consumerism" movements in the U.S. and other countries have struggled to reach critical mass and influence. However, public opinion polls taken since the late 1980s have shown consistently that a significant percentage of consumers in the U.S. and elsewhere profess a strong willingness to favor environmentally conscious products and companies. One of green marketing's challenges is the lack of standards or public consensus about what constitutes "green," according to Joel Makower, a writer on green marketing. This lack of consensus—by consumers, marketers, activists, regulators, and influential people—has slowed the growth of green products, says Makower, because companies are often reluctant to promote their green attributes, and consumers are often skeptical about claims.

Despite these challenges, green marketing has continued to gain adherents, particularly in light of growing global concern about climate change. This concern has led more companies to advertise their commitment to reduce their climate impacts, and the effect this is having on their products and services.

Greenhouse gas reduction market
The emerging greenhouse gas reduction market can potentially catalyze projects with important local environmental, economic, and quality-of-life benefits. The Kyoto Protocol's Clean Development Mechanism (CDM), for example, enables trading between industrial and developing nations, providing a framework that can result in capital flows to environmentally beneficial development activities. Although the United States is not participating in the Kyoto Protocol, several US programs enable similar transactions on a voluntary and regulatory basis.

While international trade in greenhouse gas reduction holds substantial promise as a source of new funding for sustainable development, this market can be largely inaccessible to many smaller-scale projects, remote communities, and least developed localities. To facilitate participation and broaden the benefits, several barriers must be overcome, including a lack of market awareness among stakeholders and prospective participants; specialized, somewhat complicated participation rules; and the need for simplified participation mechanisms for small projects, without which transaction costs can overwhelm the financial benefits of participation. If the barriers are adequately addressed, greenhouse gas trading can play an important role in supporting activities that benefit people's lives and the environment.

Ongoing debate
The popularity of such marketing approach and its effectiveness is hotly debated. Supporters claim that environmental appeals are actually growing in number–the Energy Star label, for example, now appears on 11,000 different companies' models in 38 product categories, from washing machines and light bulbs to skyscrapers and homes. However, despite the growth in the number of green products, green marketing is on the decline as the primary sales pitch for products. Shel Horowitz, a green marketer for over 30 years and primary author of Guerrilla marketing Goes Green states that to market effectively, green businesses need to market to three different audiences, "deep green," "lazy green," and "nongreen", and that each must be approached differently. Each will have different trigger points that will move them to buy, and for the nongreen audience, marketing effectively usually requires emphasizing product superiority rather than care for the planet. On the other hand, Roper's Green Gauge shows that a high percentage of consumers (42%) feel that environmental products don't work as well as conventional ones. This is an unfortunate legacy from the 1970s when shower heads sputtered and natural detergents left clothes dingy. Given the choice, all but the greenest of customers will reach for synthetic detergents over the premium-priced, proverbial "Happy Planet" any day, including Earth Day. New reports, however show a growing trend towards green products.

The demand for green-oriented products has been a boom to the firms that supply them. New markets emerge for recycled building products, packaging, paper goods, and even sweaters and sneakers, as well as, more efficient appliances lighting, heating, and cooling systems in homes and offices. Some green options are more expensive than traditional products and initiatives. This could learn to exploitation which is common enough that it even had produced the term greenwashing. Consumers need to question whether a firm is spending significantly more money and time advertising being green and operating with consideration for the environment than actually spending these resources on environmentally sound practices.

Confusion
One challenge green marketers – old and new –  are likely to face as green products and messages become more common is confusion in the marketplace. "Consumers do not really understand a lot about these issues, and there's a lot of confusion out there," says Jacquelyn Ottman (founder of J. Ottman Consulting and author of "Green Marketing: Opportunity for Innovation.") Marketers sometimes take advantage of this confusion, and purposely make false or exaggerated "green" claims. Critics refer to this practice as "green washing".

Greenwashing
Corporations are increasingly recognizing the benefits of green marketing, although there is often a thin line between doing so for its own benefit and for social responsibility reasons. The term “greenwashing” refers to all industries that adopt outwardly green acts with an underlying purpose to increase profits. The primary objective of greenwashing is to provide consumers with the feeling that the organization is taking the necessary steps to responsibly manage its ecological footprint. In reality, the company may be doing very little that is environmentally beneficial The term greenwashing was first used by environmentalist Jay Westerveld when objecting to hotelier's practice of placing notices in hotel rooms which asked their guests to reuse towels to “save the environment”. Westerveld noted that there was little else to suggest that the hoteliers were interested in reducing their environmental impacts, and that their interest in washing fewer towels seemed to be motivated by a concern to save costs rather than the environment. Since then greenwashing has become a central feature of debates about marketing communications and sustainability, with “awards” for greenwashing established and numerous campaigns, law and advice developed in an attempt to reduce or curb it.

Benefit corporations
In January 2012, Patagonia became the first brand to register for benefit corporation status.

A benefit corporation is an alternative to its standard counterpart as it operates under the legal premise of 1) creating a positive impact socially and environmentally in its materials, 2) uphold corporate social responsibility in terms of considering its workers, its community, and the environment as well as challenge its current boundaries in those areas, and 3) report its activity as a company as well as its achievements in social and environmental areas publicly using a non-partisan third party source.

Statistics
According to market researcher Mintel, about 12% of the U.S. population can be identified as True Greens, consumers who seek out and regularly buy so-called green products. Another 68% can be classified as Light Greens, consumers who buy green sometimes. "What chief marketing officers are always looking for is touch points with consumers, and this is just a big, big, big touch point that's not being served," says Mintel Research Director David Lockwood. "All the corporate executives that we talk to are extremely convinced that being able to make some sort of strong case about the environment is going to work down to their bottom line."

Adoptability
In 1989, 67 percent of Americans stated that they were willing to pay 5-10 percent more for ecologically compatible products. By 1991, environmentally conscious individuals were willing to pay between 15-20 percent more for green products. Today, more than one-third of Americans say they would pay a little extra for green products

An important challenge facing marketers is to identify which consumers are willing to pay more for environmentally friendly products. It is apparent that an enhanced knowledge of the profile of this segment of consumers would be extremely useful.

Everett Rogers, communication scholar and author of “Diffusion of Innovations”, claims that the following five factors can help determine whether a new idea will be adopted or not, including the idealism of the shift towards “green”:
 * 1) Relative advantage: is the degree to which the new behavior is believed to accrue more beneficial outcomes than current practice.
 * 2) Observability: is how easy it is to witness the outcomes of the new behavior.
 * 3) Trialability: is the ease with which the new behavior can be tested by an individual without making a full commitment.
 * 4) Compatibility: is the degree to which the new behavior is consistent with current practice.
 * 5) Complexity: is how difficult the new behavior is to implement.

LOHAS
LOHAS stands for Lifestyles of Health and Sustainability, and describes an integrated, rapidly growing market for goods and services that appeal to consumers whose sense of environmental and social responsibility influences their purchase decisions. The Natural Marketing Institute's (short: NMI) estimates the US LOHAS consumer market of products and services to be US$209 billion – sold across all consumer segments.

The five LOHAS segments as defined by NMI include:
 *  LOHAS: Active environmental stewards dedicated to personal and planetary health. These are the heaviest purchasers of green and socially responsible products and the early adopters who influence others heavily.
 *  Naturalites: Motivated primarily by personal health considerations. They tend to purchase more LOHAS consumable products vs. durable items.
 *  Drifters: While their intentions may be good, DRIFTERS follow trends when it is easy and affordable. They are currently quite engaged in green purchasing behaviours.
 *  Conventionals: Pragmatists who embrace LOHAS behaviour when they believe they can make a difference, but are primarily focused on being very careful with their resources and doing the ‘right’ thing because it will save them money.
 *  Unconcerned: Either unaware or unconcerned about the environment and societal issues mainly because they do not have the time or the means – these consumers are largely focused on getting by.

The green marketing mix
A model green marketing mix contains four "P's":

 * Product: A producer should offer ecological products which not only must not contaminate the environment but should protect it and even liquidate existing environmental damages.
 * Price: Prices for such products may be a little higher than conventional alternatives. But target groups like for example LOHAS are willing to pay extra for green products.
 * Place: A distribution logistics is of crucial importance; main focus is on ecological packaging. Marketing local and seasonal products e.g. vegetables from regional farms is more easy to be marketed “green” than products imported.
 * Promotion: A communication with the market should put stress on environmental aspects, for example that the company possesses a CP certificate or is ISO 14000 certified. This may be publicized to improve a firm's image. Furthermore, the fact that a company spends expenditures on environmental protection should be advertised. Third, sponsoring the natural environment is also very important. And last but not least, ecological products will probably require special sales promotions.

Additional social marketing "P's" that are used in this process are:

 * Publics: Effective Social Marketing knows its audience, and can appeal to multiple groups of people. "Public" is the external and internal groups involved in the program. External publics include the target audience, secondary audiences, policymakers, and gatekeepers, while the internal publics are those who are involved in some way with either approval or implementation of the program.
 * Partnership: Most social change issues, including "green" initiatives, are too complex for one person or group to handle. Associating with other groups and initiatives to team up strengthens the chance of efficacy.
 * Policy: Social marketing programs can do well in motivating individual behavior change, but that is difficult to sustain unless the environment they're in supports that change for the long run. Often, policy change is needed, and media advocacy programs can be an effective complement to a social marketing program.
 * Purse Strings: How much will this strategic effort cost? Who is funding the effort?

The level of greening—strategic, quasi-strategic, or tactical—dictates what activities should be undertaken by a company. Strategic greening in one area may or may not be leveraged effectively in others. A firm could make substantial changes in production processes but opt not to leverage them by positioning itself as an environmental leader. So although strategic greening is not necessarily strategically integrated into all marketing activities, it is nevertheless strategic in the product area.

Ecolabels
An individual's belief that an environmental claim lacks honesty can have a negative effect on attitude toward a brand. If, on the other side, the consumer grants credibility to the claim, the individual will behave more respectfully toward the environment. The problem in extending that credibility to a brand is that consumers interested in ecological products generally are skeptical of commercial advertisements. This skepticism is due to various factors such as lack of language, the absence of scientific knowledge necessary to interpret advertising meaning, and, in particular, the falsehoods and exaggeration of some advertising techniques. To resolve this problem, independent organizations may choose to guarantee messages on the environmental benefits of brands with environmental labeling systems sponsored by independent organizations. This practice tries to diminish perceived biases in environmental information by promoting standardization of the information with the aim of improving confidence in the evaluation of environmental benefits of products—all of which should positively affect the purchase intention.

Life-cycle assessment
During the late 1980s, new instruments such as life-cycle assessment (LCA) were invented which allowed ecological considerations to be introduced into marketing decisions.

The life cycle assessment model seeks to identify the main types of environmental impact throughout the life cycle of a product. LCA was developed according to ISO 14040. The main goal of the LCA is to define the energy and environmental profile of the finished products. The reasons to use LCA arose from the need to have a precise process accounting and to highlight potential improvements that could be used in order to increase the environmental, energy and economic efficiency and overall effectiveness of the processes. In addition, the purpose was to quantify the environmental advantages deriving from the use of recycled raw material.

Example for LCA
LCA is used for example in the building sector. Buildings today account for the 40% of the world's energy use. The resulting carbon emissions are substantially higher than those of the transportation sector. New buildings using more energy than necessary are being built every day, and millions of today's inefficient buildings will remain standing until at least 2050. It's therefore necessary to start reducing energy use in new and existing buildings in order to reduce the planet's energy-related carbon footprint. Growing interest, space, and attention in the architecture sector are directed to environmental issues according to the principles of green building. Mineral, vegetable, or animal materials such as perlite, vermiculite, rock wool, glass wool, cork, plant fibers (cotton, flax, hemp, coconut), wood fiber, cellulose, and sheep's wool can be used for the production of insulation panels.

Phillips's "Marathon" CFL lightbulb
Philips Lighting's first shot at marketing a standalone compact fluorescent light (CFL) bulb was Earth Light, at $15 each versus 75 cents for incandescent bulbs. The product had difficulty climbing out of its deep green niche. The company re-launched the product as "Marathon," underscoring its new "super long life" positioning and promise of saving $26 in energy costs over its five-year lifetime. Finally, with the U.S. EPA's Energy Star label to add credibility as well as new sensitivity to rising utility costs and electricity shortages, sales climbed 12 percent in an otherwise flat market.

Electronics sector
The consumer electronics sector provides room for using green marketing to attract new customers. One example of this is HP's promise to cut its global energy use 20 percent by the year 2010. To accomplish this reduction below 2005 levels, The Hewlett-Packard Company announced plans to deliver energy-efficient products and services and institute energy-efficient operating practices in its facilities worldwide.

Products and services
Now companies are offering more eco-friendly alternatives for their customers. Recycled products for example, are one of the most popular alternatives that can benefit the environment. These benefits include sustainable forestry, clean air, energy efficiency, water conservation, and a healthy office. One example, is the E-commerce business and office supply company Shoplet which offers a web tool that allows you to replace similar items in your shopping cart with greener products.

title: Green marketing


text:
Wikipedia talk:Education program archive/University of California, Berkeley/(SGP) Berkeley Water Group Idea Lab (Spring 2015)/Course description

This course page is a resource for students within the Berkeley Water Group Idea Lab. BWGIL students are participating in a pilot program with Wiki Ed aiming to encourage extracurricular editing through student projects. Students will be asked to make contributions to articles related to water, sanitation, and hygiene on Wikipedia. On this page please find links to our online resources, trainings, and more. For questions, contact Samantha at<EMAIL_ADDRESS>This Course Page may change. Check back for updates as Spring semester continues.

([ Click to return to your main course page and continue.])


text:
Quirino Provincial Board

The Quirino Provincial Board is the Sangguniang Panlalawigan (provincial legislature) of the Philippine province of Quirino.

The members are elected via plurality-at-large voting: the province is divided into two districts, each having four seats. A voter votes up to four names, with the top four candidates per district being elected. The vice governor is the ex officio presiding officer, and only votes to break ties. The vice governor is elected via the plurality voting system province-wide.

The districts used in appropriation of members is not coextensive with the legislative district of Quirino; unlike congressional representation which is at-large, Quirino is divided into two districts for representation in the Sangguniang Panlalawigan.

Aside from the regular members, the board also includes the provincial federation presidents of the Liga ng mga Barangay (ABC, from its old name "Association of Barangay Captains"), the Sangguniang Kabataan (SK, youth councils) and the Philippine Councilors League (PCL). Quirino's provincial board also has a reserved seat for its indigenous people (IPMR).

Current members
These are the members after the 2019 local elections and 2018 barangay and SK elections:

 * Vice Governor: Julius Vaquilar (PDP–Laban)

title: Quirino Provincial Board


text:
Radio Shariat

Radio Shariat (meaning Islamic law) was the mouthpiece of the Taliban-ruled Islamic Emirate of Afghanistan, broadcasting religious programs and official decrees and announcements. The broadcasts were carried over twenty transmitting towers. It was the foreign media's main source of information from the Taliban.

Early in the United States invasion of Afghanistan, on October 8, 2001, U.S. forces bombed the main building and antennas of Radio Shariat. The U.S. then utilized the same frequencies to broadcast music with instrumental accompaniments (which had been banned by the Taliban) as well as announcements and information in Dari and Pashto.

The U.S. bombing of the station was decried by members of the international media.

title: Radio Shariat


text:
User:HenryTehFourth

Generally, I make small edits for clarification and grammar. I don't generally make big edits to anything, because I don't have time to do a lot of research on most subjects.

I also contribute to ويكيبيدية.

Feel free to message me if I made a mistake or if you just want to say hi.

title: User:HenryTehFourth


text:
Template:Welcome and advise

Thank you for your contribution to Wikiversity. Please consider carefully which Wikimedia project Wikibooks, Wikipedia or Wikiversity your contribution would help the most. Wikiversity welcomes most types of learning materials that are not encyclopedia or textbook  articles. Please note that Wikiversity is not a place for duplication of other Wikimedia projects.

Wikiversity has adopted a "learn by doing" model for online education and encourages the creation of learning activities for Wikiversity participants. Everyone is invited to help add useful content to Wikiversity. If you need help learning how to add content, see the editing tutorial and Welcome, newcomers. Use instructions. In many cases, this template can be placed on Wikiversity pages that have some educational content, but that existing content seems like an encyclopedia article or a part of a textbook. For a description of this template and related templates, see: Welcome templates Note: when you use this template, if the page was created by a registered user, please make sure that their user talk page has the Welcome template.

title: Template:Welcome and advise


text:
Wiktionary talk:Translations/Hiding translations

 * from Wiktionary talk:Translations Rod (A. Smith) 21:50, 3 November 2007 (UTC)

<<IP_ADDRESS> 16:47, 3 Jun 2005 (UTC)>There exist a great many languages in the world. Any user is not interest in most of them. If every meaning of a word has to be translated in, say, 200 languages, the entry would become unreadable. I suggest you think of a means to hide all translations except user chose ones.

 * This could be very nice in my opinion, if it could be implemented. --Zinon
 * Agreed. I was going to write something along the same lines with regard to some sort of template for translations. The code is unreadable as well. Davilla 09:56, 24 July 2005 (UTC)

 * Yes! Please! Russian is a perfect example of why this (or a complete rethinking of the layout for translations) is a great idea! 90% of the page is translations -- and I was just looking for a simple definition. Ewlyahoocom 12:40, 7 February 2006 (UTC)

 * The template has just been coded. Syntax is as follows:

 * This yields the pleasing result of:

 * French: cacher les traductions
 * Japanese: 訳語を隠す yakugo o kakusu

 * Korean: 역어를 잠추기 yŏgŏ rul jamch'ugi
 * Portuguese: esconder as traduções

 * See the entry book for a more detailed example.
 * I will put a note on the main page to always use this template for entries with more than ten translations, and to consider using it for all translations.--Aaronsama 13:14, 12 October 2006 (UTC)

We already have a set of three templates that do the job. , and. SemperBlotto 13:18, 12 October 2006 (UTC)


text:
Operating System Design/Case studies

The goal of this book is to discuss the different issues involved in operating system design, the different strategies that have been tried and to provide concrete examples where possible. Given the number of open-source operating systems available, specific implementations will be used as examples where possible.

Example Operating Systems
Naturally, open source operating systems lend themselves to teaching more than proprietary operating systems. The source code of all the following operating systems is available free of charge online:

 * Linux
 * Net/Free/OpenBSD
 * Solaris
 * MINIX
 * GNU Hurd
 * XOK
 * ReactOS

While the following operating systems are closed source, enough is known about their implementation that they can all be used as specific examples of approaches to various OS design issues and tasks.

 * Mac OS X
 * Microsoft Windows 9x
 * Windows NT
 * QNX
 * DOS
 * HP-UX
 * AIX
 * BeOS

Example filesystems

 * FAT
 * NTFS
 * ext4

Case Study Areas
The following areas of operating system design can all be illustrated with specific examples from real operating systems. In some cases different approaches to the same task can be seen within one OS. For example, many operating systems support multiple file system types.

 * Loading the operating system
 * Initialising the operating system for use
 * Managing tasks (processes)
 * Managing memory
 * File systems and storage management
 * User interfaces

For example, in the "Managing tasks" section we might use the example of task management in a single tasking operating system like DOS, as well as some of the different scheduling algorithms that have been used in various multitasking operating systems.

The case study can include comparative analysis about any concept of different operating systems or comparison between the different versions of same operating systems. It can include the total functionality of the operating system given.

title: Operating System Design/Case studies