videolectures.net/w3cworkshop2011_bittersmann_browsers

Preview meta tags from the videolectures.net website.

Linked Hostnames

5

Thumbnail

Search Engine Appearance

Google

https://videolectures.net/w3cworkshop2011_bittersmann_browsers

Internationalization (or the lack of it) in current browsers

I'll address two common i18n problems that users of current mainstream browsers face. Users should get content from multilingual Web sites automatically in a language they understand, hence they need a way to tell their preferences. Some browsers give users this option, but others don't. I'll demonstrate live if and how languages can be set in various browsers and discuss the usability issue that browser vendors have to deal with: the trade-off between functionality and a simple user interface. Users should also be able to enter email addresses with international domain names into forms. That might not be possible in modern browsers that already support HTML5's new email input type. I'll show how to validate email addresses not being too restrictive and eventually raise the question: Does the HTML5 specification have to be changed to reflect the users' needs? Author´s presentation is available online at http://bittersmann.de/talks/multilingualweb-pisa/slides/.



Bing

Internationalization (or the lack of it) in current browsers

https://videolectures.net/w3cworkshop2011_bittersmann_browsers

I'll address two common i18n problems that users of current mainstream browsers face. Users should get content from multilingual Web sites automatically in a language they understand, hence they need a way to tell their preferences. Some browsers give users this option, but others don't. I'll demonstrate live if and how languages can be set in various browsers and discuss the usability issue that browser vendors have to deal with: the trade-off between functionality and a simple user interface. Users should also be able to enter email addresses with international domain names into forms. That might not be possible in modern browsers that already support HTML5's new email input type. I'll show how to validate email addresses not being too restrictive and eventually raise the question: Does the HTML5 specification have to be changed to reflect the users' needs? Author´s presentation is available online at http://bittersmann.de/talks/multilingualweb-pisa/slides/.



DuckDuckGo

https://videolectures.net/w3cworkshop2011_bittersmann_browsers

Internationalization (or the lack of it) in current browsers

I'll address two common i18n problems that users of current mainstream browsers face. Users should get content from multilingual Web sites automatically in a language they understand, hence they need a way to tell their preferences. Some browsers give users this option, but others don't. I'll demonstrate live if and how languages can be set in various browsers and discuss the usability issue that browser vendors have to deal with: the trade-off between functionality and a simple user interface. Users should also be able to enter email addresses with international domain names into forms. That might not be possible in modern browsers that already support HTML5's new email input type. I'll show how to validate email addresses not being too restrictive and eventually raise the question: Does the HTML5 specification have to be changed to reflect the users' needs? Author´s presentation is available online at http://bittersmann.de/talks/multilingualweb-pisa/slides/.

  • General Meta Tags

    10
    • title
      Internationalization (or the lack of it) in current browsers
    • title
      Pause
    • title
      Mute
    • title
      Subtitles
    • title
      Playback speed
  • Open Graph Meta Tags

    5
    • og:title
      Internationalization (or the lack of it) in current browsers
    • og:description
      I'll address two common i18n problems that users of current mainstream browsers face. Users should get content from multilingual Web sites automatically in a language they understand, hence they need a way to tell their preferences. Some browsers give users this option, but others don't. I'll demonstrate live if and how languages can be set in various browsers and discuss the usability issue that browser vendors have to deal with: the trade-off between functionality and a simple user interface. Users should also be able to enter email addresses with international domain names into forms. That might not be possible in modern browsers that already support HTML5's new email input type. I'll show how to validate email addresses not being too restrictive and eventually raise the question: Does the HTML5 specification have to be changed to reflect the users' needs? Author´s presentation is available online at http://bittersmann.de/talks/multilingualweb-pisa/slides/.
    • og:image
      https://apiminio.videolectures.net/prod-vln/videos/30831/thumbnail/w3cworkshop2011_bittersmann_browsers.1.v-tb.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=masoud%2F20250821%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250821T002017Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=c60f61ff1726b4254f2dace185e53f34826a7f9f5f4e040f0ab1eabc18b1ba6c
    • og:url
      https://videolectures.net/videos/w3cworkshop2011_bittersmann_browsers
    • og:type
      website
  • Twitter Meta Tags

    4
    • twitter:title
      Internationalization (or the lack of it) in current browsers
    • twitter:description
      I'll address two common i18n problems that users of current mainstream browsers face. Users should get content from multilingual Web sites automatically in a language they understand, hence they need a way to tell their preferences. Some browsers give users this option, but others don't. I'll demonstrate live if and how languages can be set in various browsers and discuss the usability issue that browser vendors have to deal with: the trade-off between functionality and a simple user interface. Users should also be able to enter email addresses with international domain names into forms. That might not be possible in modern browsers that already support HTML5's new email input type. I'll show how to validate email addresses not being too restrictive and eventually raise the question: Does the HTML5 specification have to be changed to reflect the users' needs? Author´s presentation is available online at http://bittersmann.de/talks/multilingualweb-pisa/slides/.
    • twitter:image
      https://apiminio.videolectures.net/prod-vln/videos/30831/thumbnail/w3cworkshop2011_bittersmann_browsers.1.v-tb.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=masoud%2F20250821%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250821T002017Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=c60f61ff1726b4254f2dace185e53f34826a7f9f5f4e040f0ab1eabc18b1ba6c
    • twitter:card
      summary_large_image
  • Link Tags

    15
    • icon
      ./assets/favicon.ico
    • modulepreload
      chunk-HRIFR6VR.js
    • modulepreload
      chunk-77JXALW5.js
    • modulepreload
      chunk-BL4TTXX3.js
    • modulepreload
      chunk-4RYQESEZ.js

Links

16