Showing posts with label Language. Show all posts
Showing posts with label Language. 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

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.

Sunday, December 28, 2014

GeoLocation, And Our Use Of Blogger

Recently, we've seen signs of confusion, from people who have problems with their Internet service, which shows them moving around their geographic region.
I logged in to Blogger, with no problem, yesterday. Today, after logging in successfully, I am asked for more details, to prove my identity!!
This blog owner has a problem with location based security.

Not all Blogger blog owners or readers understand that Country Code Alias Redirection, and the ability to access one's Blogger / Google account (and prevent others from accessing it), both depend upon the ability to determine the geographical location of each blog reader.

Various Google features, like Country Code Alias Redirection, and Google login, use geolocation, to identify the location of each reader.

For people using the Internet, Geolocation uses the Internet connection, to determine physical location. Unfortunately, for many blog owners, the Internet Service Provider, the Internet connection, and the Internet customer (or Blogger blog reader) may each be in a different location.

My own location - even when I am at home - may, at times, appear to move in a 30 mile radius. My ISP routes my connection through any of half a dozen different connection points, in my region, depending upon current network activity.

Some smaller ISPs, located near a country border, may actually get service through a larger ISP in another country. Customers of the smaller ISP may appear, through geolocation, to reside in the other country.

This can be an unfortunate problem, with country code alias redirection, with language detection, with login authentication, and / or the Location option in Post Editor.

People located in one country, reading an unfamiliar language, or seeing their latest post show up in the wrong province / state - or even country - may not appreciate the confusion which is caused. And people who login, and appear to move from city to city in the region, grow tired of having to prove their identity - after successfully entering account name and password.

Thanks to domain based filtering, this may become a security issue for some blog owners, near country borders, who may not be able to maintain / publish their blogs.

Unfortunately, geolocation, using the Internet Address (aka "IP" address), will never return consistent and precise results. Any location based processes will always provide fuzzy results, thanks to Internet services which load balance their network connections.

Tuesday, December 1, 2009

Nitecruzr Dot Net Et Al With New Language Bar Design

This month, Roberto (of Robertos Blogs) and I present a new Cumulus Language Bar, with better designed buttons, plus an enhanced complement of 54 different languages.

In Make Your Blog Speak More Languages, you will find the updated code block, with the new language complement.

We hope that you will enjoy the new look!

>> Top

Wednesday, November 11, 2009

Multi-Lingual Blogging Requires Language Selections

Occasionally, we see requests from folks who want to publish a blog in non English languages, and don't trust the Google Translator, or translated blogs using a Translator Gadget.

Every different world language has its own peculiarities - character set, font, grammatical constructions, even direction of type will differ from language to language. To support these peculiarities, Blogger has a language selection, for each language which they support. This roughly parallels the ongoing development of the Google Translator.

Use the Language selector for your blog, at Settings - "Language and formatting", and look at the Language pull-down list.

Select your own language, before you publish in the blog.

When you publish a non English blog, find and select the language of your interest, before you publish posts. This may present a challenge, to those who want to produce a blog in more than one language, simultaneously. Any blog can have one and only one language selection.

If you publish multiple blogs, merge them in a cluster.

If you want to publish in, say, English and French, you'll need two blogs - an English blog and a French blog, each in the right language selection. To publish in English, French and German, you'll need three blogs - an English blog, a French blog, and a German blog, each in the right language selection.

Having setup an cluster or set of blogs, combine and merge them into a cohesive set, so it all looks like one blog, to your readers. And use "hreflang" to aggregate the cluster, to the search engines.

A solid naming convention helps enable future expansion.

If I want to publish The Real Blogger Status in English, French, and German, I could have "de-blogging-nitecruzr.blogspot.com", "en-blogging-nitecruzr.blogspot.com", and "fr-blogging-nitecruzr.blogspot.com", each blog with its proper language selection. Since I publish in my own domain, "Nitecruzr.Net", I would have "de.blogging.nitecruzr.net", "en.blogging.nitecruzr.net", and "fr.blogging.nitecruzr.net".

I use the ISO 2 character Language Codes for all my multi-lingual blog names.

Friday, September 19, 2008

Following - For (Not Quite) All

Those of us who have been enjoying following the development of the Blogger Following global community may have observed the Blogger Buzz announcement of September 11.
Now it's available to all users in English.


Since not everybody that uses Blogger speaks English (nor is English even the most common language of the world population), this doesn't quite indicate a global release of the product. And those of you who do speak English may want to check your language settings, and make sure that your Blog and Profile languages are set to English. Hopefully, you'd already know that, but maybe not everybody has this as a priority.

So what happens if your Blog or Profile Language is set to something other than "English"? If you try to add the Following gadget to one of your blogs, you might observe the advice (in French, for instance)
Ce gadget est experimental. Il n'est pas encore disponible sur tous les blogs.
the keyword here being experimental.

See Roberto's Report: Following - Which Languages? for details about this discovery, particularly if English is not your primary language.

>> Top

Thursday, September 11, 2008

Nitecruzr Dot Net Et Al Is Now Available In 24 Languages

Following a rather intense effort yesterday, by Roberto of Roberto's Blogs, all 23 languages currently available in the Google On The Fly Web Page Translator are now part of the Cumulus Translator Bar.

We hope to see more languages made available by Google, in the future. As they come out in the Google Translator, we plan to add them to the Translator Bar, straightaway.

For a more pictorial description of the Translator Bar, and it's development process, see Roberto's Report: Language Translator Set-up.

>> Top

Navigate» Become author for this Blog