Search results

Jump to navigation Jump to search
  • ...<code>ID</code> as well as <code>class</code>? In other words, if I know I'm gong to have only one review or only one location, or whatever, on a page,
    8 KB (1,152 words) - 16:28, 18 July 2020
  • === Proposal: <code>m-*</code> values === <span class="m-weight">
    56 KB (8,114 words) - 21:06, 26 July 2023
  • * I'm not sure whether it makes sense to do GEDCOM as its own format, the FAM str
    7 KB (1,089 words) - 16:22, 18 July 2020
  • I'm using this page to collect brainstorms on additions to the [[process]] for
    8 KB (1,114 words) - 16:31, 18 July 2020
  • ...ing</code> seems to be used instead of <code>sparkle:version</code>, and I'm not sure why.
    12 KB (1,857 words) - 16:21, 18 July 2020
  • ** +1 [[User:DavidJanes|David Janes]]. I'm thinking of this as Entry Replies, which would be physically represented as ** [[User:DavidJanes|David Janes]] I'm happy to have whatever made up by parser implementers, which seems to be th
    22 KB (3,311 words) - 22:58, 13 July 2022
  • >eve@example.net</a> for corrections. (I know I'm not the most trustworthy
    13 KB (1,947 words) - 16:35, 18 July 2020
  • In the proposal above, the "version" class name is used, but I'm not happy about it. In other microformats, "version" is used to indicate th
    10 KB (1,570 words) - 16:21, 18 July 2020
  • *m
    10 KB (1,529 words) - 16:22, 18 July 2020
  • * +1 I'm tending to agree with the removal of version, as in practice it has not bee
    9 KB (1,316 words) - 16:26, 18 July 2020
  • *** I'm not suggesting that we create a new microformat using rev — I'm pointing out that if we define <code>rel=fan</code> (for linking to your fa
    23 KB (3,631 words) - 16:35, 18 July 2020
  • ''If I'm a fan of someone, what XFN rel value should I use when linking to them?''
    11 KB (1,785 words) - 16:35, 18 July 2020
  • ...Location_dec_US all images tagged in Wikimedia Commons] using decimal or D-M-S values have geo markup. Example:
    14 KB (2,150 words) - 16:22, 18 July 2020
  • *** +1 Though I'm worried about tools catching up to this change. [[User:EdwardOConnor|Ted]]
    12 KB (1,889 words) - 16:21, 18 July 2020
  • ...ser:ntoll|Nicholas Tollervey]] (can't make it all the way to Brighton... I'm north of London) :-(
    13 KB (2,032 words) - 16:22, 18 July 2020
  • ...br title="guideline created due to one or more actions by Manu Sporny">src:M</abbr>([http://microformats.org/discuss/mail/microformats-new/2009-February If your post to the list starts off "I'm new to the list and microformats so I don't know if you've discussed this a
    31 KB (4,800 words) - 16:23, 20 October 2021
  • ...onorific suffixes (e.g. Jr., Sr., II, III, etc. as opposed to Ph.D., Esq., M.D., etc.)?'' ...br element. <code>&lt;abbr title="[MiddleName]" class="additional-name"&gt;M&lt;/abbr&gt;</code>. Honorific Suffixes in the RFC include Jr., Esq. and ot
    36 KB (5,726 words) - 16:26, 18 July 2020
  • ...e to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, tho
    16 KB (2,415 words) - 23:18, 16 February 2023
  • ...s en ligne (pages web, fichiers) jusqu'aux critiques de critiques en elles-même. ...ntifier le même objet/item/produit à travers différents sites de commerce, même s'il est quelque part très utile d'en disposer, est ici hors du champ
    36 KB (5,424 words) - 16:27, 18 July 2020
  • ...ent trouvée et partagée, elle la publierait avec [[hcard-fr|hCard]]. De la même manière, si une organisation est en train de planifier une série d'é ...ong>auteurs/designers web qui puissent facilement les ajouter</strong> eux-mêmes. Ajouter des microformats est par exemple plus facile que de publier u
    12 KB (1,786 words) - 16:35, 18 July 2020

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)