From Fedora Project Wiki

  • ...e JSON" messages are mainly due to a syntax mismatch. Ensure "fas-name" is lowercase. (You can also try wrapping the rest of your profile with '''noinclude''' s
    2 KB (289 words) - 11:03, 15 December 2022
  • ...e (zh_CN)||{{result|fail|zh_CN}}||{{bz|950571}}||Some shortcut keys are in lowercase letters. And a lot of translation are outdated or inaccurate. It needs a bi
    2 KB (338 words) - 07:32, 14 November 2013
  • ''Some of the beginning pages can be numbered as lowercase Roman numerals. I'm counting them as normal pages so we can get a full page
    8 members (3 subcategories, 1 file) - 17:07, 16 March 2009
  • ...wer element. So 'b' is newer than 'a', 'add' is newer than 'ZULU' (because lowercase characters win in <code>strcmp</code> comparisons), and 'aba' is newer than
    5 KB (866 words) - 18:41, 25 June 2009
  • # Font package naming uses the lowercase form.
    4 KB (586 words) - 02:43, 25 February 2009
  • ...kages are named '''[foundryname-]projectname[-fontfamilyname]-fonts''', in lowercase.
    5 KB (584 words) - 02:39, 25 February 2009
  • ...erican Proprietary Typefaces, ed. David Pankow. The primary source for the lowercase is the original Centaur specimen booklet by Lanston Monotype, London, 1929.
    4 KB (500 words) - 16:48, 12 November 2010
  • ...his accepts a numerical log level or the well-known syslog symbolic names (lowercase): emerg, alert, crit, err, warning, notice, info, debug.
    4 KB (613 words) - 17:13, 14 June 2015
  • <br />Lowercase with periods and a preceding space. To form the plural of an acronym, add a trailing, lowercase s with no apostrophe, e.g., ROMs, PINs.
    19 KB (2,737 words) - 14:45, 22 March 2014
  • Keywords can be in all uppercase or all lowercase.
    9 KB (1,442 words) - 19:11, 15 August 2015
  • [11:40] * scop would love all lowercase names, everywhere, period [11:42] <spot> i'm not seeing any reasons to actually mandate lowercase vs mixedcase
    27 KB (3,909 words) - 18:54, 17 February 2010
  • ...nt-dap-</code>, which is followed by the name of the Assistant itself, all lowercase. For example, the DAP named <code>Openscad</code> will be named <code>devas
    8 KB (1,176 words) - 14:02, 12 March 2015
  • Wiki changes the image file names that start with lowercase to uppercase.<br/> eg. this image with name lowercase.png will convert the image file name <br/>
    21 KB (3,369 words) - 19:34, 2 October 2021
  • ...ever, if they do not express any preference of case, you should default to lowercase naming.<BR> ...s must be named '''[foundryname-]projectname[-fontfamilyname]-fonts''', in lowercase. For a full explanation, see [[Packaging/FontsPolicy#Naming]].
    16 KB (2,511 words) - 15:13, 17 May 2017
  • ...ever, if they do not express any preference of case, you should default to lowercase naming.<BR> ...s must be named '''[foundryname-]projectname[-fontfamilyname]-fonts''', in lowercase. For a full explanation, see [[Packaging/FontsPolicy#Naming]].
    17 KB (2,589 words) - 11:57, 16 May 2017
  • * Naming all packages in lowercase ...otes that "Even historic mixed-case packages like X have been converted to lowercase over time." is pretty much false.
    41 KB (6,186 words) - 03:24, 21 December 2008
  • ...nt-dap-</code>, which is followed by the name of the Assistant itself, all lowercase. For example, the DAP named <code>Openscad</code> will be named <code>devas
    8 KB (1,175 words) - 19:57, 21 December 2018
  • #* network manager comes up in search in lowercase, great, cap don't matter
    9 KB (1,617 words) - 14:33, 20 October 2009
  • * that was lowercase and not punctuated
    6 KB (938 words) - 13:30, 18 September 2016
  • ...import from MoinMoin May 2008) Doc date is 2007. requests package names be lowercase when possible.
    20 KB (2,423 words) - 18:54, 27 February 2009
View ( | ) (20 | 50 | 100 | 250 | 500)