RE: [WSG] Marking Up Poems
not always, but often. esp if it ends in beer and a party From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Paul Bennett [EMAIL PROTECTED] Sent: Friday, 20 June 2008 12:12 PM To: 'wsg@webstandardsgroup.org' Subject: RE: [WSG] Marking Up Poems Must you Australian's *always* have the last say? ;) *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** NOTICE - This communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking any action in reliance on, this communication by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient of this communication please delete and destroy all copies and telephone SMS Management Technology on 9696 0911 immediately. Any views expressed in this Communication are those of the individual sender, except where the sender specifically states them to be the views of SMS Management Technology. Except as required by law, SMS Management Technology does not represent, warrant and/or guarantee that the integrity of this communication has been maintained nor that the communication is free from errors, virus, interception or interference. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] Multiple Language Domains
there's lots of things u can do to ensure that the language is correctly identified and the right characterset it used 1. as sajan suggests, the setting locale is important. it also helps with time/date formats e.g. for php: setlocale(constant,location) (see also: http://www.w3schools.com/php/func_string_setlocale.asp) 2. define the page's _primary_ language of the page content in the header html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en 3. define the language inline when it changes from one language to another within the content SPAN id=msg1 class=info lang=fr 4. use the uft-8 characterset and define it in the header through the doctype ?xml version=1.0 encoding=UTF-8? !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en 5. use css to define the font to use for different languages. p lang=zh class=zh(some Chinese text)/p /* in the css */ [lang=zh], * html .zh { font: 800 14pt/16.5pt Li Sung, serif } viola! M :) From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Sajan Franco [EMAIL PROTECTED] Sent: Saturday, 14 June 2008 6:42 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Multiple Language Domains Hi Paul, one way is to ask the user to choose a Locale on the landing page such en_EN or en_US , where en is the language chosen by the user and EN would represent the country. For instance in countries like Belgium and Switzerland, most of the websites ask the user to choose their locale before proceeding so that the website can serve content of their choice in the language they prefer. An example of this is http://www.nissan.ch/ or http://www.sunsilk.com where the user can chose the locale and proceed further. Since the translations are in different directories it is search engine friendly too. So when a user choose a locale he is taken to the respective homepage which serves the user in the language of his preference. But as far as usability is concerned I am not sure because both of cited examples feature flash, which I suppose is not that user friendly when you take accessibility into consideration. Warm Regards Sajan Franco On Sat, Jun 14, 2008 at 12:39 AM, Paul McCann [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi Guys, I am currently in the middle of building a site which has to be bi-lingual. We have two domains for the site www.ourwales.org.ukhttp://www.ourwales.org.uk and www.cymruni.org.ukhttp://www.cymruni.org.uk I am looking for suggestions/help on how to handle the two domains. Currently ourwales is the prominant/main domain and the one to which the IP details of the site are set. We are then using an alias within apache to also point cymruni to the same site. So you see the same site when you visit, but have two different domains. Both these domains are advertised. I have a few worries though, currently both domains point to the english language version of the site, this will be changed so cymruni goes to the Welsh language side. Although the language is the same and its possible for people to flip between the two languages is it possible that google will see the site as duplicate content? Also we are having trouble getting the alias to append the lang=cy to it on first visit. My thought was to make the ourwales domain the prominant one, and set up a folder with a 301 redirect in it which says cymruni.orghttp://cymruni.org has moved permanantly to ourwales.org.uk/lang=cyhttp://ourwales.org.uk/lang=cy that way we have only one domain indexed. The reason for writing to this group is two fold 1, how does this affect usability and what is 'best practice' in this situation? 2, How have/would you implement a problem like this? Ideally we want to provide the smoothest and friendliest experience to both the user and SE whichever domain they use. thanks Paul *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** NOTICE - This communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking any action in reliance on, this communication by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient
RE: [WSG] Should we design for 800x600 screens?
I've also seen a lot of people with big screens re-size their browser windows to about 1024x768/800x600-ish. M From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of David Hucklesby [EMAIL PROTECTED] Sent: Wednesday, 11 June 2008 3:46 PM To: wsg@webstandardsgroup.org Cc: IceKat Subject: Re: [WSG] Should we design for 800x600 screens? On Tue, 10 Jun 2008 13:28:18 +1000, IceKat wrote: Hi, I have a question I'd like to poll people about. Should we still bother designing to fit in with 800x600 screen resolutions or is it Ok to just design for 1024x768 and not worry about smaller resolutions? I know applications like Google Desktop make it more complicated and am interested to hear people's views. FWIW - I work at a computer training lab, teaching computer skills to a very wide age group. A significant number of students switch the nominally 1280 x 960 19 display to 800 x 600. Just my 41 cents. Cordially, David -- *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** NOTICE - This communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking any action in reliance on, this communication by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient of this communication please delete and destroy all copies and telephone SMS Management Technology on 9696 0911 immediately. Any views expressed in this Communication are those of the individual sender, except where the sender specifically states them to be the views of SMS Management Technology. Except as required by law, SMS Management Technology does not represent, warrant and/or guarantee that the integrity of this communication has been maintained nor that the communication is free from errors, virus, interception or interference. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] Should we design for 800x600 screens?
what about mobile browsing? the iphone is having quite the impact on mobile computing and designing to 800x600 is going to mean you're likely making information inaccessible and un-usable designing to a screen size is like designing to one browser my advice - 1. profile your users and know who they are, what they want, what they need, what their online behaviour 2. turn profile information into functional and non-functional (design) requirements 3. design to meet those needs 4. validate design solutions with those users 5. re-assess needs on a regular basis m From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Anton Babushkin [EMAIL PROTECTED] Sent: Tuesday, 10 June 2008 3:39 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Should we design for 800x600 screens? I would say Absolutely, absoutely and absolutely! My reasoning for this is simple: what about the rest of those users who don't browse the internet with the browser in full screen? As a matter of fact I'm doing it right now, so thank god GMail scales gracefully, or I probably wouldn't use it! I think the big question is how scalable your web page becomes beyond 800x600 and that all really depends on the kind of content your web site is providing. If its something which can be extremelly useful for a Google Desktop application then perhaps you need to take that into account. If not, then perhaps rethink your strategy/approach. Thats my two cents. On Tue, Jun 10, 2008 at 1:28 PM, IceKat [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi, I have a question I'd like to poll people about. Should we still bother designing to fit in with 800x600 screen resolutions or is it Ok to just design for 1024x768 and not worry about smaller resolutions? I know applications like Google Desktop make it more complicated and am interested to hear people's views. IceKat PS- If this has been asked before I apologise and ask if it's possible to see mail archives to see the responses. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] *** -- - Anton Babushkin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** NOTICE - This communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking any action in reliance on, this communication by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient of this communication please delete and destroy all copies and telephone SMS Management Technology on 9696 0911 immediately. Any views expressed in this Communication are those of the individual sender, except where the sender specifically states them to be the views of SMS Management Technology. Except as required by law, SMS Management Technology does not represent, warrant and/or guarantee that the integrity of this communication has been maintained nor that the communication is free from errors, virus, interception or interference. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***