Showing posts with label Internationalisation. Show all posts
Showing posts with label Internationalisation. Show all posts

Thursday, March 15, 2018

Publish To Your Readers In Multiple Languages

Some blog owners speak / write in multiple languages - and want to interact with their different readers, separately, in each different language.

Blogger, and Google, support the need for publishing multiple blogs, each written in a different language. The "hreflang" tag, added to a blog, identifies other blogs, published to different languages, with identical or similar content.

There are three ways to provide content, in multiple languages.
  • Publish one blog, with posts published in different languages.
  • Publish one blog, and add the Google Translate gadget.
  • Publish multiple blogs, one language / blog, linked using "hreflang".

You can publish a single blog with multiple posts written in different languages - if you wish.

Mixing multiple posts in different languages creates a compromise.

One blog, mixing posts written in different languages, will be a compromise. Each different world language has its own character set, phrasing, spelling, syntax, and other characteristics.

If you publish extensively, you will get better results publishing multiple blogs, each blog with content in one language. Your readers will appreciate reading a blog, that's published in one language - their own language.

Best results come from multiple blogs, in one language for each blog.

Blogger lets us indicate a language for any blog, in Settings - Language and formatting. One blog == one language.

If you want to publish content in multiple languages, and have everything properly indexed by the search engines, you can create an "hreflang" blog cluster - with each blog published in its own language.

To get the best result from "hreflang", you publish similar content, equally to each blog - and add "hreflang" tags identically to each blog.

If I was tri-lingual, I could publish a set of blogs in English, French, and Spanish.

Si j'étais trilingue, je pourrais publier un ensemble de blogs en anglais, français et espagnol.

Si fuera trilingüe, podría publicar un conjunto de blogs en inglés, francés y español.

I could publish three blogs to BlogSpot.

  1. en-blogging-nitecruzr.blogspot.com
  2. fr-blogging-nitecruzr.blogspot.com
  3. es-blogging-nitecruzr.blogspot.com

In the template header, for each blog, I would add three complementary tags.

<link rel="alternate" hreflang="en" href="http://en-blogging-nitecruzr.blogspot.com/" />
<link rel="alternate" hreflang="fr" href="http://fr-blogging-nitecruzr.blogspot.com/" />
<link rel="alternate" hreflang="es" href="http://es-blogging-nitecruzr.blogspot.com/" />

Multiple blogs, properly intercnnected, gives improved search results.

As any one blog in the cluster is being indexed, the "href=" in the tags links to the other two blogs - just like any three blogs being cross linked. This gives search indexing between all three blogs, equally.

For improved search reputation, based on three "identical" blogs, this technique can't be beat.

You can publish one blog, indexed in one language, and translated when needed.

You don't have to use "hreflang", to publish content written in multiple languages. If you only want to write in one language, and let readers to read your blog in their own language, you can use Google Translate.

Look in the sidebar, of this blog. Google Translate ("Translate Me") lets every world resident read a blog in their own language - when they select their language.

Just add a Google Translate gadget to your one blog, using the "Add a Gadget" wizard, on the Layout dashboard page. Each reader, surfing to your one blog, can use the gadget to translate to their language, as necessary - as long as they:
  • Understand the gadget header "Translate Me" (or however you name your gadget).
  • Know to use the "Select Language" pull down list.
  • Know how to locate their own language in the list.
The "Google Translate" gadget is labeled in English. The French people use "français" when describing their naive tongue - and call our language "Anglais", not English.

The language list, in French, will be in a different order. Other languages will be even more challenging. If you examine a language list, on a blog written in Chinese, could you locate their label for "English"?

Writing in each different language is much more respectful, to people who don't read English.

With a blog using Google Translate, the blog content is indexed, only using the published language. Readers who don't read in your native language will never find your blog, when they search in their language.

To index content in multiple languages, use "hreflang".

If you want to develop a reader audience in multiple language groups, you can use "hreflang" to publish multiple blogs, each written and indexed in one specific language. Each of your potential readers can search, in their own language, and find your blog.

And none of your readers have to know - or care - that a blog is published in other languages.



There are several ways to provide blog content in multiple languages, depending upon how relevant you want to be, to your readers, in their various "foreign" languages - and how much work you are willing to do.

Tuesday, March 22, 2016

Custom Domain Publishing, And World Culture

People who speak (read / write) languages, that do not use Roman character sets, need to publish in their native language - and the Internet now supports that need.

Some registrars will register domains which use non Roman character sets, in the URL. Not all Internet services will accept non Roman characters, however.

My favourite online DNS diagnostic services, DigWebInterface, and intoDNS, and Rex Swain's HTTP Viewer, only use ASCII. One cannot use non ASCII ("non Roman") characters, with either service.

"بحث-سناب.com", as converted, shows an example of an Internationalized domain name.

To use DigWebInterface to retrieve DNS addresses, and intoDNS to check the domain setup, we have to convert the native URL to Ascii.

I use three reliable online services, which will convert URLs to ASCII.


Converting "بحث-سناب.com" to ASCII involves use of one of the latter services.


DomainTools




WhoIs - Identity for everyone




Who.is - Powered by Name.com



Using the 3 tools, we see that "بحث-سناب.com" == "xn----zmcbcml8b0j.com", "XN----ZMCBCML8B0J.COM", and "xn----zmcbcml8b0j.com", respectively. Look carefully, in the body of the display for each service, for the IDN equivalent.

We can then use "xn----zmcbcml8b0j.com", with DigWebInterface, and intoDNS - and get the necessary diagnostics.

And using the latter tools, we see a properly setup domain - which is now being used for a properly published Blogger blog, verified in Rex Swain.


DigWebInterface




intoDNS




Rex Swain's HTTP Viewer



And when assistance is requested, in Blogger Help Forum: Get Help with an Issue, we can use these tools with non Roman character URLs.

There may be limitations, though.

Here is a blog published to "www.राजभाषाअनुभाग.भारत" - aka "www.xn--l1b0bn3cxacq2d2ccbd1b.xn--h2brj9c".







The IDN concept has now led to another domain name concept - "emoji" domains.

Some people have taken the ability to setup a domain, using non Roman characters, to another level. How about a domain name, which includes a smiley face?

This is a limited use feature. Maybe, the limit will save us?

The availability of emoji domains is limited. As of August 2017, there are eight top-level domains for which registration is possible, all of which are ccTLDs: .ai, .cf, .ga, .gq, .ml, .tk, .to, and .ws.

This is intriguing - but is it useful?



If people don't know how to "type" it, how will new readers access the blog? Will search engines index it? Does the Blogger "Create a blog" wizard actually support it?

The jury is still out, here. ".whatever" vanity TLDs started this trend. I'm not sure where this will go, with TLD "emoji" domains.

Houston, we may have a problem with TLDs that are IDN encoded.

For a TLD that is in English ("بحث-سناب.com"), both of these work:

http://www.digwebinterface.com/?hostnames=xn----zmcbcml8b0j.com%0D%0Awww.xn----zmcbcml8b0j.com&type=A&useresolver=8.8.4.4&ns=auth&nameservers=

https://intodns.com/xn----zmcbcml8b0j.com

For a TLD that is IDN encoded (राजभाषाअनुभाग.भारत"), we have mixed success.

This works:

http://www.digwebinterface.com/?hostnames=xn--l1b0bn3cxacq2d2ccbd1b.xn--h2brj9c%0D%0Awww.xn--l1b0bn3cxacq2d2ccbd1b.xn--h2brj9c&type=A&useresolver=8.8.4.4&ns=auth&nameservers=

This does not work:

https://intodns.com/check/?domain=%E0%A4%B0%E0%A4%BE%E0%A4%9C%E0%A4%AD%E0%A4%BE%E0%A4%B7%E0%A4%BE%E0%A4%85%E0%A4%A8%E0%A5%81%E0%A4%AD%E0%A4%BE%E0%A4%97.%E0%A4%AD%E0%A4%BE%E0%A4%B0%E0%A4%A4



The Internet now supports use of non ASCII characters, in URLs. In order to publish #Blogger blogs to Internationalised Domain Names, we need to convert native URLs to ASCII - using any one of three identified online DNS services.


https://productforums.google.com/forum/#!category-topic/blogger/qKWZ0807m60

https://productforums.google.com/forum/#!category-topic/blogger/L1pv6CPUK18

Sunday, January 11, 2015

Google Domains Is Not Yet Available, Worldwide

Some would be domain owners are reporting the sad truth about Google Domains.
I tried to use a Google Domains invitation, and got a refusal.
We're sorry. You appear to be in a country where Google Domains is not yet available. You may search for domains, but you will not be able to purchase a domain unless you have a U.S. billing address. Learn more

Get notified when Google Domains is available in your country.
So thanks anyway!
Google Domains is currently a beta product - and as of December 2017, it is available in 14 countries.

This is a normal strategy, used by Google - beta products are typically deployed on a country by country basis.

Google Domains offers distinct advantages, over "Buy a domain" and registrar direct domain purchases.

  • They will control the purchase - and offer a more stable bank payment process.
  • They will control the DNS infrastructure - and offer a more stable setup process, and ongoing blog access.
  • They provide excellent real time support, 7 x 24 basis.

Google Domains are available in a few countries - with more being added, periodically.



As of March 2018, Google Domains may be available in 15 countries - Australia, Brazil, Canada, France, India, Indonesia, Italy, Japan, Mexico, Netherlands, Spain, Thailand, UK, USA, and Vietnam. If you live in any of the other 180+ countries, you have to use GoDaddy - or another third party registrar.

Deploying a bank payment network, and a DNS infrastructure (to name two details), on a world wide basis, won't happen immediately.

It's all too easy to overlook the international issues, when dealing with Blogger and Google. My apology to those of you who were unduly excited, for nothing.

Have patience, your time will come.

Monday, January 5, 2015

Inviting Comments To Your Blog Is Not Cut And Dried

Blog owners are periodically asking themselves
How do I invite my readers to leave comments?
Some blog owners think of commenting as the most important way to get new readers.

One of the most seemingly insignificant components of the Blogger template is the link to invite the readers to leave comments. This is not a simple feature - it varies according to where the comment form is placed, and to different language and style decisions.

Variations
There are four comment form placement options, for Blogger blogs.
  1. Embedded.
  2. Full page.
  3. Pop up window.
  4. Dynamic template.
There are two display contexts.
  1. Index page view (archive retrieval, label search, main page).
  2. Post page view.
Some blog owners may confuse index page view, with "Show at most" set to "1 Post", to post page view. This won't be the case. "Show at most" will only apply to main page view. And main page display with only one post displayed, without jump break, will still be index page view.

Some blog owners may confuse index page view, with "Show at most" set to "1 Post", to post page view. This won't be the case. "Show at most" will only apply to main page view. And main page display with only one post displayed, without jump break, will still be index page view.

The placement option, added to the display context, creates a combination of various needs for phrasing the simple caption, which I will call for example
Please, leave a comment!
That simple invitation can vary according to the the nationality of the blog owner, and to the nature of the blog.

Blog Language
Comments is an English word. Every blog that's published in a non English language has a different word for "comments".
  • en français: commentaires.
  • in italiano: commenti.
  • en español: comentarios.
And some languages phrase plurals significantly.
  • 0 comments.
  • 1 comment.
  • 2 comments.
Very few blog owners publish a blog in (USA) English, and want the blog captioned with "1 comments", or "2 comment".

Long ago, somebody decided that inviting comments would be easier, if a blog with 0 comments was captioned with "No comments". Then, another grammar expert (lawyer?) decided that "No comments" could be interpreted by some people as "We don't want comments!".

Blog Nature
Then, some blog owners don't like the word "comments", they feel that the word should be changed, to reflect the nature of their blog. For my blog, "Chucks Musings", I would use "musings", instead of "comments" (but with dynamic templates, that option is not yet available). Other blog owners have used "dreams", "introspections", and "wanderings" (to name a few).

Form Placement
One of the most controversial features of comments is the limitation of displaying the individual comments, and the comment form, only beneath the individual posts. On the main page, for all comment placement options, you will see the comment caption "No comments", "1 comment", etc - which then links to the display of existing comments - and to the form to publish a comment.

All existing placement options now display existing comments only beneath the individual posts. With the full page and popup window options, a link captioned "Post a Comment" then leads to the comment form itself.

With the full page and popup window form, for the convenience of the owner and reader, existing comments are displayed there also. And, wherever the comment form is displayed, so must be the hated CAPTCHA form.

The Reader's Language
To further the confusion, some blog features are automatically translated into the readers language - when the reader is logged in to Blogger / Google, and when the reader's login status and Blogger profile can be determined by the blog display. In some cases, the readers location is used.

Sometimes, both the blog owner and reader could read / speak different languages, neither being English. Not every world citizen understands "Please, leave a comment!" - or even "Post a Comment". And some blogs are published in French - and read in both Italian and Spanish.

The Tower Of Babel
The Tower Of Babel is not going away, in this lifetime.

Navigate» Become author for this Blog