• Login
    • Search
    • Categories
    • Recent
    • Tags
    • Users
    • Groups
    • Rules
    • Help

    Do more on the web, with a fast and secure browser!

    Download Opera browser with:

    • built-in ad blocker
    • battery saver
    • free VPN
    Download Opera

    Learning programming

    Lounge
    5
    49
    15565
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Former User
      A Former User last edited by

      Take some fun - open it in browser: http://www.facebook.com/download/580457528747854/button (1).html

      Reply Quote 0
        1 Reply Last reply
      • sgunhouse
        sgunhouse Moderator Volunteer last edited by

        What is the difference between "code", "kbd" and "samp" elements?

        Formatting. You may want text that is supposed to be typed in to look different - most often, in boldface in some monospaced font. By having separate tags they can format it differently.

        Reply Quote 0
          1 Reply Last reply
        • A Former User
          A Former User last edited by

          Hey! I've created a coffeecup-image chart (html), and in the header titled it using partially Cyrillic letters.
          The problem is, when I opened it in my Opera (11), its title appeared corrupt: "ßíäåX coffeecup".
          Well, I went to check the code - yeah, it was the same in the code; I tried retyping - same shit; I changed fonts to MS Sans Serif, retyped - o'k, saved, reloaded in the browser - same shit (I reopened the doc in my Notepad - it appeared o'k there!); opened the source in Opera, retyped there, clicked "apply" - it's got "????X coffeecup" altogether*:doh:*

          What's wrong with this picture?
          In the [applied] source (which is still open in a tab now) the title looks o'k: "<head><title>ЯндеX coffeecup</title></head>"😕

          Edit/add:
          Struck to recheck the doc after the "applying": hey, it's "<head><title>????X coffeecup</title></head>" there too!
          Well, and I'd closed that source here in browser - and reopened it now: same "<head><title>????X coffeecup</title></head>" there now too!:doh:

          What is it?
          Some fonts incompatibility?
          I didn't check the html in my other browsers yet*😕*

          Reply Quote 0
            1 Reply Last reply
          • sgunhouse
            sgunhouse Moderator Volunteer last edited by

            Platform? Some older versions of Windows don't like mixed encodings in title bars.

            You might be able to achieve the same effect by typing the text in a comment, then setting Opera's encoding to something incorrect (for this site, "correct" being either Automatic selection or UTF-8).

            Reply Quote 0
              1 Reply Last reply
            • A Former User
              A Former User last edited by

              Platform?

              Where is it?
              Windows XP SP3.

              Yes, and with Chrome, here in my yesterday posts the input looks the same.
              Now I'll probably try opening the doc here... Yeah, same "????X".
              Opening the source... Yeah, same "<head><title>????X coffeecup</title></head>" with that MS Sans Serif there...
              😕

              Reply Quote 0
                1 Reply Last reply
              • A Former User
                A Former User last edited by

                By the way, I can't seem to edit the code here in Chrome - while I could in my Opera yesterday*:)*

                Reply Quote 0
                  1 Reply Last reply
                • A Former User
                  A Former User last edited by

                  Yes, and with Chrome, here in my yesterday posts the input looks the same. Now I'll probably try opening the doc here... Yeah, same "????X". Opening the source... Yeah, same "<head><title>????X coffeecup</title></head>" with that MS Sans Serif there... 😕

                  Now opened it in my Firefox (it's 3.6.6!).
                  It had the same "????X" title. I edited the images a bit...
                  Then - in the very end, before closing the Notepad - I thought there'd be no harm to retry the mixed title...
                  No, I didn't change any fonts; I just deleted those question marks and typed "Янде" there, saved, reloaded in browser - TA-DA! :jester:
                  It appeared exactly what it had been and was supposed to be, ie just great/right*:yes:* Well - it's in my senior Firefox: same OS, bla-bla - but works! 🆙
                  😛

                  Reply Quote 0
                    1 Reply Last reply
                  • A Former User
                    A Former User last edited by

                    Now I created another html with not only a "mixed" title but also Cyrillic [plain] text in the body. And again no matter how I try to edit/change fonts, it's only correctly displayed in my Firefox 3.6.
                    Actually, this Firefox is the only one on here which is properly Russian-localised - it even originates from a Russian source.
                    I have these poops here:

                    :dunno: .íåçíàþ. :hi: .privet. :bye: .poka. :tut: .àéàé. :walla: .îáñòåíó. :spammer: .ïèøó. 🇭🇲 .chic. .hehe. .olen'. .elk. .êîëäóí.

                    When I edited that in my Opera's "source code", those became "?????"s as it did that time with my previous doc in question.
                    I tried tinkering with Opera's font settings - no avail.
                    What's wrong with it? Shall I use certain metatags in the header - like to style the document?
                    Why do some browsers not handle Cyrillic by default with the HTML5 doctype?

                    Reply Quote 0
                      1 Reply Last reply
                    • A Former User
                      A Former User last edited by

                      And again no matter how I try to edit/change fonts, it's only correctly displayed in my Firefox 3.6.
                      Actually, this Firefox is the only one on here which is properly Russian-localised - it even originates from a Russian source.

                      Now I launched another Firefox I have installed - 4.0, and initially - at the very start, while loading - the "Coffeecup" doc's title was displaying o'k for a moment – then it turned to "ßíäåX coffeecup" as it always was in those two other browsers (Operapresto pseudo-Russian & Google Chrome Br-En).
                      Forgot to mention that this version of Firefox is localised British English too - as my Google Chrome is*:happy:*
                      Well, now I'm about to check this other - later - document here in 4.0... Yup, both the title and that Cyrillic content are "messed up" as they are in those two aforementioned browsers...

                      Reply Quote 0
                        1 Reply Last reply
                      • sgunhouse
                        sgunhouse Moderator Volunteer last edited by

                        Did you try checking your encoding? Characters that are not allowed in a given encoding become question marks, whereas characters that don't exist in a font become boxes.

                        Reply Quote 0
                          1 Reply Last reply
                        • A Former User
                          A Former User last edited by

                          What encoding? I didn't encode the Cyrillic letters - I just typed them in there.

                          They become question marks only when I try editing that shit (retype them anew) in a "page source" tab in my Opera. If I type them in in the Notepad, right there they look nice - while in those but one browsers it's "ßíäåX" and "àéàé" (I copypaste that from the source and page itself - just loaded, while there in the doc(s) they look perfectly Cyrillic as well as directly copypasted from there the very same in here - "ЯндеX coffeecup").

                          Well, and I ain't got no boxes. :norris:

                          Reply Quote 0
                            1 Reply Last reply
                          • Deleted User
                            Deleted User last edited by

                            Setting a charset shows correct title in browser!

                            &lt;!DOCTYPE html&gt;
                            &lt;html&gt;
                            &lt;head&gt;
                            &lt;meta http-equiv=&quot;content-type&quot; content=&quot;text/html; charset=UTF-8&quot;&gt; &lt;!-- charset must be set! --&gt;
                            &lt;title&gt;Янде Coffee Cup&lt;/title&gt;&lt;/head&gt;
                            &lt;body&gt;
                            &lt;button type=&quot;button&quot; onclick=&quot;alert('Give Miiii Coffiieeeee!')&quot;&gt;Do not disturb my Coffieeeeee!&lt;/button&gt;
                            &lt;/body&gt;
                            &lt;/html&gt;
                            
                            Reply Quote 0
                              1 Reply Last reply
                            • A Former User
                              A Former User last edited by

                              What do these meta attributes do exactly?

                              <!-- charset must be set! -->

                              Well, I haven't learned about this element yet, but so far they didn't include that in their example codes...

                              I wonder what?
                              Why is it that one browsers "corrupt" those Cyrillic while others do just fine with it?
                              Yesterday I thought of an idea to check the codes of some Russian sites/pages which are plenty and whose Cyrillic doesn't get "corrupt" in those "corrupting browsers" in that way... I'm up to that yet. :rolleyes:

                              Reply Quote 0
                                1 Reply Last reply
                              • A Former User
                                A Former User last edited by

                                Well, so far I've taken a look at two of such (Russian pages).
                                The first one's declaration heavily resembled non-5 HTML (so far as I can judge), the next one's looks more HTML5ish (well, it's still not it):

                                !DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

                                This site (page) does have a 'mixed' title too:

                                <title>Dubna.RU &bull; Дубна.Рф &bull; Прогноз погоды</title>

                                ...So far I can't see any meta-charset there, but there's this:

                                <link rel="stylesheet" type="text/css" href="/styles.css" />

                                The only "language" thing I can see so far is this <script> element (still in the head - last but two):

                                <script type="text/javascript" src="http://apis.google.com/js/plusone.js"> {lang: 'ru'} </script>


                                So, so far I haven't found an html5 page with a 'mixed' title yet...
                                ...ahm..:wait:

                                Reply Quote 0
                                  1 Reply Last reply
                                • Deleted User
                                  Deleted User last edited by

                                  <meta http-equiv="content-type" content="text/html; charset=UTF-8"> tells the browser to use UTF-8 as charencoding to get all charcters in HTML correctly interpreted.

                                  Dependent of your OS and Texteditor with Russian language you can have UTF-8 or KOI8-R or ISO 8859-5 or Windows-1251
                                  See
                                  https://de.wikipedia.org/wiki/KOI8
                                  https://de.wikipedia.org/wiki/Windows-1251
                                  https://de.wikipedia.org/wiki/ISO_8859-5

                                  Reply Quote 0
                                    1 Reply Last reply
                                  • A Former User
                                    A Former User last edited by

                                    <meta http-equiv="content-type" content="text/html; charset=UTF-8"> tells the browser to use UTF-8 as charencoding to get all charcters in HTML correctly interpreted.

                                    Well, are these attributes/values proper in HTML5?
                                    And another question stays: why do certain browsers (version(s) of) handle those/my pages when they do not contain any metas at all?

                                    Reply Quote 0
                                      1 Reply Last reply
                                    • Deleted User
                                      Deleted User last edited by

                                      Well, are these attributes/values proper in HTML5?

                                      The element META is allowed with attribute http-equv in HTML5.
                                      See
                                      http://www.w3.org/TR/html5/document-metadata.html
                                      http://www.w3.org/TR/html5/document-metadata.html#attr-meta-http-equiv-content-type
                                      http://www.w3.org/TR/html5/document-metadata.html#attr-meta-http-equiv

                                      And another question stays: why do certain browsers (version(s) of) handle those/my pages when they do not contain any metas at all?

                                      Some browsers do have a default fallback, if charencoding is missing. Some browsers guess which encoding it could be. On some servers the correct encoding is send by a HTTP header. On some servers the incorrect encoding is send by a HTTP header.

                                      Reply Quote 0
                                        1 Reply Last reply
                                      • A Former User
                                        A Former User last edited by

                                        Some browsers do have a default fallback, if charencoding is missing. Some browsers guess which encoding it could be.

                                        But if I amend my htmls with that charset - will those "good" browsers do not mind it? Like "Gosh! Master added a 'charset' - let me break then!"?🙂

                                        Reply Quote 0
                                          1 Reply Last reply
                                        • Deleted User
                                          Deleted User last edited by

                                          will those "good" browsers do not mind it?

                                          Well, they might mind or not.

                                          You can trust me, i'm webdevoloper and have more or less bad experiences with browsers and websites over years 😉

                                          Reply Quote 0
                                            1 Reply Last reply
                                          • A Former User
                                            A Former User last edited by

                                            will those "good" browsers do not mind it?

                                            Well, they might mind or not.

                                            Well... then I'll investigate some more Russian sites' codes first... :rolleyes:
                                            You mind?:)

                                            Reply Quote 0
                                              1 Reply Last reply
                                            • First post
                                              Last post

                                            Computer browsers

                                            • Opera for Windows
                                            • Opera for Mac
                                            • Opera for Linux
                                            • Opera beta version
                                            • Opera USB

                                            Mobile browsers

                                            • Opera for Android
                                            • Opera Mini
                                            • Opera Touch
                                            • Opera for basic phones

                                            • Add-ons
                                            • Opera account
                                            • Wallpapers
                                            • Opera Ads

                                            • Help & support
                                            • Opera blogs
                                            • Opera forums
                                            • Dev.Opera

                                            • Security
                                            • Privacy
                                            • Cookies Policy
                                            • EULA
                                            • Terms of Service

                                            • About Opera
                                            • Press info
                                            • Jobs
                                            • Investors
                                            • Become a partner
                                            • Contact us

                                            Follow Opera

                                            • Opera - Facebook
                                            • Opera - Twitter
                                            • Opera - YouTube
                                            • Opera - LinkedIn
                                            • Opera - Instagram

                                            © Opera Software 1995-