Stories
Slash Boxes
Comments

Dev.SN ♥ developers

posted by martyb on Sunday January 11 2015, @02:19PM   Printer-friendly
from the named-character-entities:-"-&-<->-…-—-£ dept.

named character entities: " & < > … — £

Saved as "Plain Old Text"

Preview looked correct.

Looked correct in the stories Submissions queue.

This discussion has been archived. No new comments can be posted.
Display Options Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by martyb on Sunday January 11 2015, @03:48PM

    by martyb (76) on Sunday January 11 2015, @03:48PM (#28214) Journal

    See: 14.12 Update [soylentnews.org]:

    Input vs Output Wackiness

    Currently if you put html entities in and hit preview they get transformed into literal characters.

    <blockquote>preceding text entered as: named-character-entity-less-than blockquote named-character-entity-greater-than

    Looked correct when I pressed preview... am pressing preview again.

    Nice! still see what looks like a blockquote HTML element!

    Previewed again; saw no change in appearance.

    Am now pressing Submit button

    • (Score: 2) by martyb on Sunday January 11 2015, @03:50PM

      by martyb (76) on Sunday January 11 2015, @03:50PM (#28215) Journal

      See: 14.12 Update [soylentnews.org]:

      Input vs Output Wackiness

      Currently if you put html entities in and hit preview they get transformed into literal characters.

      <blockquote>preceding text entered as: named-character-entity-less-than blockquote named-character-entity-greater-than

      Looked correct when I clicked the Preview button

      Am now clicking on the Submit button.

      • (Score: 2) by martyb on Sunday January 11 2015, @03:54PM

        by martyb (76) on Sunday January 11 2015, @03:54PM (#28216) Journal

        Allowed HTML
        <b|i|p|br|a|ol|ul|li|dl|dt|dd|em|strong|tt|blockquote|div|ecode|quote|strike|sarc|sarcasm>

        Trying sarc:
        <sarcasm>witt are you looking at?</sarcasm>

        Trying sarcasm:
        <sarcasm>witt are you looking at?</sarcasm>

        • (Score: 2) by martyb on Sunday January 11 2015, @03:58PM

          by martyb (76) on Sunday January 11 2015, @03:58PM (#28217) Journal

          Allowed HTML <b|i|p|br|a|ol|ul|li|dl|dt|dd|em|strong|tt|blockquote|div|ecode|quote|strike|sarc|sarcasm>

          Trying sarc: <sarcasm>witt are you looking at?</sarcasm>

          Trying sarcasm: <sarcasm>witt are you looking at?</sarcasm>

          Looks like an HTML element entered as sarc is translated into being sarcasm...

          Let's see what happens with mixed case:

          Trying SARC: <sarcasm>SARC</sarcasm>

          Trying Sarc: <sarcasm>Sarc</sarcasm>

          Trying sARC: <sarcasm>sARC</sarcasm>

          Space sensitive? <sarcasm> sarc </sarcasm>(That had a space after each less-than and a space before each greater-than.

          • (Score: 2) by martyb on Sunday January 11 2015, @04:02PM

            by martyb (76) on Sunday January 11 2015, @04:02PM (#28218) Journal

            Allowed HTML <b|i|p|br|a|ol|ul|li|dl|dt|dd|em|strong|tt|blockquote|div|ecode|quote|strike|sarc|sarcasm>

            Trying sarc: <sarcasm>witt are you looking at?</sarcasm>

            Trying sarcasm: <sarcasm>witt are you looking at?</sarcasm>

            Looks like an HTML element entered as sarc is translated into being sarcasm...

            Let's see what happens with mixed case:

            Trying SARCASM: <sarcasm>SARCASM</sarcasm>

            Trying Sarcasm: <sarcasm>Sarcasm</sarcasm>

            Trying sARCASM: <sarcasm>sARCASM</sarcasm>

            Space sensitive? <sarcasm> sarcasm </sarcasm>(That had a space after each less-than and a space before each greater-than.

            No closing tag around sarc: stuff1<sarcasm>stuff2

            No closing tag around sarcasm: stuff1<sarcasm>stuff2

            In preview, every instance of "sarc" within an HTML "element" (of whatever case) was converted to "sarcasm"

            • (Score: 2) by martyb on Sunday January 11 2015, @05:54PM

              by martyb (76) on Sunday January 11 2015, @05:54PM (#28219) Journal

              (Submitted as "HTML Formatted".)

              According to 14.12 Update [soylentnews.org]:

              Support for Additional Tags

              We're adding standard support for sub/sup/abbr/strike tags. We're also adding support for the custom tags sarc/sarcasm and two forms of a "user" tag.

              According to the comment submission screen:

              Allowed HTML
              <b|i|p|br|a|ol|ul|li|dl|dt|dd|em|strong|tt|blockquote|div|ecode|quote|strike|sarc|sarcasm>

              1.) I do not see the several new tags listed as being allowed?

              2.) The title="this and that" attribute for the new ABBR element has its spaces stripped.

              sub: normalsubnormal

              sup: normalsupnormal

              abbr: normalabbrnormal

              strike: normalstrikenormal

              It is unclear how the "user" tags are supposed to be coded and what they are intended to accomplish.

              • (Score: 2) by martyb on Sunday January 11 2015, @06:01PM

                by martyb (76) on Sunday January 11 2015, @06:01PM (#28220) Journal

                This sub1sub2sub3sub2sub1 that

                • (Score: 2) by The Mighty Buzzard on Sunday January 11 2015, @06:47PM

                  by The Mighty Buzzard (18) Subscriber Badge <themightybuzzard@soylentnews.org> on Sunday January 11 2015, @06:47PM (#28224) Journal

                  martyb regular old user link typed just like it looks.
                  @#76: user link using #N instead of username

                  --
                  123
                  456
                  789
                  • (Score: 2) by martyb on Monday January 12 2015, @10:47AM

                    by martyb (76) on Monday January 12 2015, @10:47AM (#28226) Journal

                    First off, it's early, I'm tired, and under-caffeinated.

                    I guess I'm missing the backstory on what the motivation for the new "user" element, what need it's meeting, its expected syntax, and expected result.

                    I understand things best from being given a set of examples. I'm frustrated as I have nothing to go on and all my attempts at using some kind of element with "user" in it have come up empty. :/ From your reply, I'm guessing the purpose is to allow someone to refer to a user on the site. Your examples suggest there are two variations.

                    1. Easily reference the user by nick: https://dev.soylentnews.org/~The+Mighty+Buzzard/ [soylentnews.org]
                    2. Easily reference the user by UID: https://dev.soylentnews.org/users.pl?uid=18 [soylentnews.org]

                    I'm also very curious about error cases... non-existent UIDs (e.g. too small, too large, non-numeric) and non-existent nicks (typo, case-sensitivity(?), etc.)

                    So, I'm still at a loss for the expected/permitted *syntax* for the new user elements, as well as what the expected output is in each case.

                    Separately, I would think this should be documented somewhere on the site, as I'll not be the only one wondering about this. (Hmm, might be useful to have a page enumerating the permitted tags/elements and give examples of each... not everyone comes to our site knowing HTML. I need to think about that one some more.)

                    I look forward to any guidance you can provide.

                  • (Score: 2) by martyb on Monday January 12 2015, @11:11AM

                    by martyb (76) on Monday January 12 2015, @11:11AM (#28227) Journal

                    Hmm, maybe you were giving me examples of the syntax of the input instead of examples of the output?

                    @The+Mighty+Buzzard

                    @#18

                    Does not appear to be the case; at least in preview, they appear exactly as I typed them. Let's try putting angle brackets around them:

                    <@The+Mighty+Buzzard>

                    <@#18>

                    I've replaced the less/greater than chars with named character entities to show what I had used; nothing was displayed in either case -- the elements were completely removed.

                    Let's try using a "user" element:

                    <user @The+Mighty+Buzzard>

                    <user @#18>

                    Same result, and same change, after the fact, to reveal what I had entered.

                    Let's try again using a syntax analagous tothe URL element:

                    <user:@The+Mighty+Buzzard>

                    <user:@#18>

                    And that caused the elements to be removed, too. Again, to show what I had entered, in the preceding I have replaced each less-than character that I had typed with its named character entity: &lt; and each greater-than with &gt;

  • (Score: 2) by martyb on Sunday January 11 2015, @06:07PM

    by martyb (76) on Sunday January 11 2015, @06:07PM (#28221) Journal

    (HTML Formatted)

    This sup1sup2sup3sup2sup1sup0 that

    (Note the extra /SUP tag added beyond those necessary to bring things back to normal)

  • (Score: 2) by martyb on Sunday January 11 2015, @06:10PM

    by martyb (76) on Sunday January 11 2015, @06:10PM (#28222) Journal

    (HTML Formatted)

    NormalsubNormal

    NormalsupNormal

    Normalsup1sub1thisthat

    Normalsub1sup1thisthat

  • (Score: 2) by martyb on Sunday January 11 2015, @06:18PM

    by martyb (76) on Sunday January 11 2015, @06:18PM (#28223) Journal
    Text before a user tag Text within a user tag Text after a user tag
  • (Score: 2) by martyb on Thursday January 15 2015, @10:39AM

    by martyb (76) on Thursday January 15 2015, @10:39AM (#28228) Journal

    Testing newly-supported abbr element. HTML Formatted

    [abbr title="North Atlantic Treaty Organization]NATO[/abbr]: NATO

    When I hovered my mouse over "NATO" in preview I saw: "NorthAtlanticTreatyOrganization" — spaces were stripped from between the words.