tag:blogger.com,1999:blog-240695952024-03-27T16:53:05.588-07:00The Real Blogger StatusWhat Blogger won't tell youNitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.comBlogger47125tag:blogger.com,1999:blog-24069595.post-27704458363544468112018-03-15T12:00:00.002-07:002018-03-20T15:06:44.360-07:00Publish To Your Readers In Multiple LanguagesSome blog owners speak / write in multiple languages - and want to interact with their different readers, separately, in each different language.<br />
<br />
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.<br />
<a name='more'></a><br />
There are three ways to provide content, in multiple languages.<br />
<ul><li>Publish one blog, with posts published in different languages.</li>
<li>Publish one blog, and add the Google Translate gadget.</li>
<li>Publish multiple blogs, one language / blog, linked using "hreflang".</li>
</ul><br />
You can publish a single blog with multiple posts written in different languages - if you wish.<br />
<br />
<b>Mixing multiple posts in different languages creates a compromise.</b><br />
<br />
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.<br />
<br />
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.<br />
<br />
<b>Best results come from multiple blogs, in one language for each blog.</b><br />
<br />
Blogger lets us indicate a language for any blog, in Settings - Language and formatting. One blog == one language.<br />
<br />
If you want to publish content in multiple languages, and have everything properly indexed by the search engines, you can <a href="http://blogging.nitecruzr.net/2015/05/publish-language-related-blog-cluster.html">create an "hreflang" blog cluster</a> - with each blog published in its own language.<br />
<br />
To get the best result from "hreflang", you publish similar content, equally to each blog - and add "hreflang" tags identically to each blog.<br />
<br />
If I was tri-lingual, I could publish a set of blogs in English, French, and Spanish.<br />
<br />
Si j'étais trilingue, je pourrais publier un ensemble de blogs en anglais, français et espagnol.<br />
<br />
Si fuera trilingüe, podría publicar un conjunto de blogs en inglés, francés y español.<br />
<br />
I could publish three blogs to BlogSpot.<br />
<br />
<ol><li>en-blogging-nitecruzr.blogspot.com</li>
<li>fr-blogging-nitecruzr.blogspot.com</li>
<li>es-blogging-nitecruzr.blogspot.com</li>
</ol><br />
In the template header, for each blog, I would <a href="http://blogging.nitecruzr.net/2015/05/hreflang-and-language-region-based-blog.html">add three complementary tags</a>.<br />
<br />
<pre><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/" />
</pre><br />
<b>Multiple blogs, properly intercnnected, gives improved search results.</b><br />
<br />
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.<br />
<br />
For improved search reputation, based on three "identical" blogs, this technique can't be beat.<br />
<br />
<b>You can publish one blog, indexed in one language, and translated when needed.</b><br />
<br />
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.<br />
<br />
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.<br />
<br />
Just add a Google Translate gadget to your one blog, using <a href="http://blogging.nitecruzr.net/2016/05/blogger-magic-using-add-gadget.html">the "Add a Gadget" wizard</a>, 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:<br />
<ul><li>Understand the gadget header "Translate Me" (or however you name your gadget).</li>
<li>Know to use the "Select Language" pull down list.</li>
<li>Know how to locate their own language in the list.</li>
</ul>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.<br />
<br />
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"?<br />
<br />
Writing in each different language is much more respectful, to people who don't read English.<br />
<br />
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.<br />
<br />
<b>To index content in multiple languages, use "hreflang".</b><br />
<br />
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.<br />
<br />
And none of your readers have to know - or care - that a blog is published in other languages.<br />
<br />
<hr /><br />
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.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-81445642720675464162016-03-22T11:48:00.000-07:002018-03-12T08:17:33.930-07:00Custom Domain Publishing, And World CulturePeople who speak (read / write) languages, that do not use Roman character sets, need to publish in their native language - and <a href="https://en.wikipedia.org/wiki/Internationalized_domain_name" target="_blank">the Internet now supports that need</a>.<br />
<br />
Some registrars will register domains which use non Roman character sets, in the URL. Not all Internet services will accept non Roman characters, however.<br />
<br />
My favourite online DNS diagnostic services, <a href="http://www.digwebinterface.com/" target="_blank">DigWebInterface</a>, and <a href="http://www.intodns.com/" target="_blank">intoDNS</a>, and <a href="http://www.rexswain.com/httpview.html" target="_blank">Rex Swain's HTTP Viewer</a>, only use ASCII. One cannot use non ASCII ("non Roman") characters, with either service.<br />
<a name='more'></a><br />
"بحث-سناب.com", as converted, shows an example of an <a href="https://en.wikipedia.org/wiki/Internationalized_domain_name" target="_blank">Internationalized domain name</a>.<br />
<br />
To use DigWebInterface to retrieve DNS addresses, and intoDNS to check the domain setup, we have to convert the native URL to Ascii.<br />
<br />
I use three reliable online services, which will convert URLs to ASCII.<br />
<br />
<ul><li><a href="http://www.domaintools.com/" target="_blank">DomainTools</a></li>
<li><a href="http://www.whois.com/" target="_blank">WhoIs - Identity for everyone</a></li>
<li><a href="http://who.is/" target="_blank">Who.is - Powered by Name.com</a></li>
</ul><br />
Converting "بحث-سناب.com" to ASCII involves use of one of the latter services.<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEicHXqEI7sJ4yLs7PPm9PEXdakDOhmuzjZyIk5kYYJyzbaANqxZaev3t88VC4hOf5OuFzn6RlMNHNt28Ev07hewrxGzuJ6bVui_VGaCWWl-46wJ9pwwPRLbgf3gixhym7-HweIGow/s1600/Screenshot+2016-03-22+at+09.12.35.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEicHXqEI7sJ4yLs7PPm9PEXdakDOhmuzjZyIk5kYYJyzbaANqxZaev3t88VC4hOf5OuFzn6RlMNHNt28Ev07hewrxGzuJ6bVui_VGaCWWl-46wJ9pwwPRLbgf3gixhym7-HweIGow/s320/Screenshot+2016-03-22+at+09.12.35.png" /></a></div><br />
DomainTools<br />
<br clear=left /><br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgD2zEJM1jvFA2qsg7wKieRv5F1HpxlTpy9ZoxiKZ9CPP5EdCwyggb7IgWP0S4s3FY3VOzmwzAUJKeAJx6GIn7RkZ8fB4zRx0_36NjP68VnYsBD0OdZRqhdRkKDJ9cnMNLf0WQXtg/s1600/Screenshot+2016-03-22+at+09.12.48.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgD2zEJM1jvFA2qsg7wKieRv5F1HpxlTpy9ZoxiKZ9CPP5EdCwyggb7IgWP0S4s3FY3VOzmwzAUJKeAJx6GIn7RkZ8fB4zRx0_36NjP68VnYsBD0OdZRqhdRkKDJ9cnMNLf0WQXtg/s320/Screenshot+2016-03-22+at+09.12.48.png" /></a></div><br />
WhoIs - Identity for everyone<br />
<br clear=left /><br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEitJgDFM7LESdezZ6oEFQeLyocZO3cuNI-HciXw98qKQifX_UzG8QxduTURh3X5DPGtTwn-hQ7ekijTheuPGCBv1R4nzjCwGZO6vuTbZ5OTTqVJmyuQaAVsC0WadvOIlIPELIuLRg/s1600/Screenshot+2016-03-22+at+09.13.16.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEitJgDFM7LESdezZ6oEFQeLyocZO3cuNI-HciXw98qKQifX_UzG8QxduTURh3X5DPGtTwn-hQ7ekijTheuPGCBv1R4nzjCwGZO6vuTbZ5OTTqVJmyuQaAVsC0WadvOIlIPELIuLRg/s320/Screenshot+2016-03-22+at+09.13.16.png" /></a></div><br />
Who.is - Powered by Name.com<br />
<br clear=left /><br />
<br />
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.<br />
<br />
We can then use "xn----zmcbcml8b0j.com", with <a href="http://www.digwebinterface.com/?hostnames=xn----zmcbcml8b0j.com%0D%0Awww.xn----zmcbcml8b0j.com&type=A&useresolver=8.8.4.4&ns=auth&nameservers=">DigWebInterface</a>, and <a href="http://www.intodns.com/xn----zmcbcml8b0j.com">intoDNS</a> - and get the necessary diagnostics.<br />
<br />
And using the latter tools, we see a properly setup domain - which is now being used for a properly published Blogger blog, verified in <a href="http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://www.xn----zmcbcml8b0j.com&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7834.60.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/49.0.2623.95+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=AUTO" target="_blank">Rex Swain</a>.<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjBCcHQWKiiY7FDU_iLKPNOPHK-wiahjMaRb1wmsSiJP43RmltFLkrHJNphUHoTZN3DZDyk4JIVOeLn-AvJPDFXFK4aQvdLNlQFeY-onv_nnTT13hz3521pUrNecQhhfhXXb25LFg/s1600/Screenshot+2016-03-22+at+09.29.42.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjBCcHQWKiiY7FDU_iLKPNOPHK-wiahjMaRb1wmsSiJP43RmltFLkrHJNphUHoTZN3DZDyk4JIVOeLn-AvJPDFXFK4aQvdLNlQFeY-onv_nnTT13hz3521pUrNecQhhfhXXb25LFg/s320/Screenshot+2016-03-22+at+09.29.42.png" /></a></div><br />
DigWebInterface<br />
<br clear=left /><br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhmKW2c7gt8z8VOKvihL0XV741uoPcxUnJ0L5iggU2fLntK3-VMZ68KXVzt6udl7SpOGe9pauijq20vkogtauleTm1HEkSGMEpCDu-DFUe6uZx340CgjjR4fgEkXNIXGF-jFDmSKA/s1600/Screenshot+2016-03-22+at+09.29.54.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhmKW2c7gt8z8VOKvihL0XV741uoPcxUnJ0L5iggU2fLntK3-VMZ68KXVzt6udl7SpOGe9pauijq20vkogtauleTm1HEkSGMEpCDu-DFUe6uZx340CgjjR4fgEkXNIXGF-jFDmSKA/s320/Screenshot+2016-03-22+at+09.29.54.png" /></a></div><br />
intoDNS<br />
<br clear=left /><br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEju54j-HeJSVjBEFVQSrPMdVpD8LjWms6jmA1ioPmctppQW1G82_G649LwUnXykc35FF2nSHr29ysVM6t9WAkmt6QlVQ0FqG7CQyaEo4VptHIIsKKG9mWzL1Hzb_BilrnobmbIRgw/s1600/Screenshot+2016-03-22+at+09.45.10.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEju54j-HeJSVjBEFVQSrPMdVpD8LjWms6jmA1ioPmctppQW1G82_G649LwUnXykc35FF2nSHr29ysVM6t9WAkmt6QlVQ0FqG7CQyaEo4VptHIIsKKG9mWzL1Hzb_BilrnobmbIRgw/s320/Screenshot+2016-03-22+at+09.45.10.png" /></a></div><br />
Rex Swain's HTTP Viewer<br />
<br clear=left /><br />
<br />
And when assistance is requested, in <a href="http://productforums.google.com/forum/?hl=en&fromgroups=#!categories/blogger/something-is-broken" target="_blank">Blogger Help Forum: Get Help with an Issue</a>, we can use these tools with non Roman character URLs.<br />
<br />
<b>There may be limitations, though.</b><br />
<br />
Here is a blog published to "www.राजभाषाअनुभाग.भारत" - aka "www.xn--l1b0bn3cxacq2d2ccbd1b.xn--h2brj9c".<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh718DUSgHZX-aMGeDx_jFb60QAT_rPdS6JORkJmmxwZyu8Ffp_KzXoyZlTlxnFN-IPNFIOSDzD-dTb9TMEVijEmYkVx-J8zG9u2HzbL1x9mnxpM9beUHrvK0v5fFaWBH2cM4DzxQ/s1600/Screenshot+2017-05-29+at+11.28.39.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh718DUSgHZX-aMGeDx_jFb60QAT_rPdS6JORkJmmxwZyu8Ffp_KzXoyZlTlxnFN-IPNFIOSDzD-dTb9TMEVijEmYkVx-J8zG9u2HzbL1x9mnxpM9beUHrvK0v5fFaWBH2cM4DzxQ/s320/Screenshot+2017-05-29+at+11.28.39.png" width="320" height="180" data-original-width="1366" data-original-height="768" /></a></div><br clear=left /><br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgsosc11Ly4OnNQKER7UmmgYchvAufUoDKnkoyDDaGou_Xt02skIhHpcUBupe_fMW-Ch7AnujgdzsZenj_tzw5ilxNCOjMkMX25_Vh3xoOfjellflhUEadIV_B1c1bPAcgUnn749A/s1600/Screenshot+2017-05-29+at+11.31.55.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgsosc11Ly4OnNQKER7UmmgYchvAufUoDKnkoyDDaGou_Xt02skIhHpcUBupe_fMW-Ch7AnujgdzsZenj_tzw5ilxNCOjMkMX25_Vh3xoOfjellflhUEadIV_B1c1bPAcgUnn749A/s320/Screenshot+2017-05-29+at+11.31.55.png" width="320" height="180" data-original-width="1366" data-original-height="768" /></a></div><br clear=left /><br />
<br />
<b>The IDN concept has now led to another domain name concept - "emoji" domains.</b><br />
<br />
Some people have taken the ability to setup a domain, using non Roman characters, to another level. How about <a href="https://en.wikipedia.org/wiki/Emoji_domain" target="_blank">a domain name, which includes a smiley face</a>?<br />
<br />
This is a limited use feature. Maybe, the limit will save us?<br />
<br />
<blockquote>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.</blockquote><br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhHZYn5DIAy9taabjTAPSaXiH6MV8OTgbhgm7fZkdjW8oZ46hT_31aa2C0wQNsz60ZGQHg5B9Bo3X21fYyewhXg4UmwJCLX6NadeLioZc8tPDPV2pJC8WjGYp0yjKxXdCElN-yZdw/s1600/Screenshot+2018-03-12+at+07.58.50+-+Edited.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhHZYn5DIAy9taabjTAPSaXiH6MV8OTgbhgm7fZkdjW8oZ46hT_31aa2C0wQNsz60ZGQHg5B9Bo3X21fYyewhXg4UmwJCLX6NadeLioZc8tPDPV2pJC8WjGYp0yjKxXdCElN-yZdw/s320/Screenshot+2018-03-12+at+07.58.50+-+Edited.png" width="320" height="213" data-original-width="838" data-original-height="559" /></a></div>This is intriguing - but is it useful?<br />
<br clear=left /><br />
<br />
If people don't know how to "type" it, how will new readers access the blog? Will search engines index it? Does <a href="http://blogging.nitecruzr.net/2012/05/creating-new-blog.html">the Blogger "Create a blog" wizard</a> actually support it?<br />
<br />
The jury is still out, here. ".whatever" vanity TLDs started this trend. I'm not sure where this will go, with TLD "emoji" domains.<br />
<br />
<b>Houston, we may have a problem with TLDs that are IDN encoded.</b><br />
<br />
For a TLD that is in English ("بحث-سناب.com"), both of these work:<br />
<br />
<blockquote><a href="http://www.digwebinterface.com/?hostnames=xn----zmcbcml8b0j.com%0D%0Awww.xn----zmcbcml8b0j.com&type=A&useresolver=8.8.4.4&ns=auth&nameservers=" target="_blank">http://www.digwebinterface.com/?hostnames=xn----zmcbcml8b0j.com%0D%0Awww.xn----zmcbcml8b0j.com&type=A&useresolver=8.8.4.4&ns=auth&nameservers=</a></blockquote><br />
<blockquote><a href="https://intodns.com/xn----zmcbcml8b0j.com" target="_blank">https://intodns.com/xn----zmcbcml8b0j.com</a></blockquote><br />
<b>For a TLD that is IDN encoded (राजभाषाअनुभाग.भारत"), we have mixed success.</b><br />
<br />
This works:<br />
<br />
<blockquote><a href="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=" target="_blank">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=</a></blockquote><br />
This does not work:<br />
<br />
<blockquote><a href="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" target="_blank">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</a></blockquote><br />
<hr /><br />
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.<br />
<br />
<br />
https://productforums.google.com/forum/#!category-topic/blogger/qKWZ0807m60<br />
<br />
https://productforums.google.com/forum/#!category-topic/blogger/L1pv6CPUK18Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-70896053301802206752016-02-11T16:52:00.002-08:002017-12-12T07:51:32.228-08:00AdSense Is A Contextual Ad Hosting ServiceAdSense requires content - substantial amounts of text content - in a supported language.<br />
<br />
The term "contextual" means that the ads, which display on each different blog, are chosen to match the subject in the posts. This assures the ad companies, which pay for the ads hosted on the blogs, that their ads will be seen by people who appreciate the products.<br />
<br />
With the ads carefully chosen, AdSense can confidently charge appropriately - and the blog owner can be paid to host the ads.<br />
<a name='more'></a><br />
The blog content is analysed, by the AdSense crawler, as it reads the posts.<br />
<br />
<b>The AdSense crawler automatically decides what ads to show, on each blog page.</b><br />
<br />
The crawler, which is similar to a search engine bot, has to be able to read the content.<br />
<br />
<ul><li>Textual content is required.</li>
<li>Supported languages are required.</li>
<li>Photo / video blogs can't qualify.</li>
<li>JavaScript based templates won't show ads.</li>
<li>Ads may be displayed day by day - or week by week.</li>
<li>Some blog subjects just won't qualify.</li>
</ul><br />
<b>Textual content is required.</b><br />
<br />
The crawler decides what the blog is about, by examining the text in the posts. The posts need to have <a href="http://blogging.nitecruzr.net/2016/02/with-adsense-ads-are-not-based-on.html">some minimum amount of text</a>, to make this work.<br />
<a name="Language"></a><br />
<b>Supported languages are required.</b><br />
<br />
AdSense ads are designed to be read by people, in their native language. Blogs written in all languages of the world won't have ads - because AdSense does not work with ad companies which sell products for people of all languages.<br />
<br />
Only blogs <a href="https://support.google.com/adsense/answer/9727" target="_blank">primarily written in supported languages</a> can host AdSense ads.<br />
<blockquote>Please also be aware that placing the AdSense code on pages with content primarily in an unsupported language is not permitted by the <a href="https://support.google.com/adsense/answer/48182" target="_blank">AdSense program policies</a></blockquote><br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEimFZgRPRi-De3uUx2QC6e6ONwv9FQSlzqgbbChwB_5exHCQQdmoB-kW8sYNvZQ56FoyHdvdDgjilDo_rIjoJ_z05JAhit0hI4618hiGSd2j2kg8q6mzY6Lv-O7eeZo-WrlkHEpnQ/s1600/Screenshot+2016-02-11+at+16.44.50.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEimFZgRPRi-De3uUx2QC6e6ONwv9FQSlzqgbbChwB_5exHCQQdmoB-kW8sYNvZQ56FoyHdvdDgjilDo_rIjoJ_z05JAhit0hI4618hiGSd2j2kg8q6mzY6Lv-O7eeZo-WrlkHEpnQ/s320/Screenshot+2016-02-11+at+16.44.50.png" /></a></div>Blogs written in Bengali cannot legally show AdSense ads, right now.<br />
<br clear=left /><br />
If an AdSense publisher uses a legally acquired account from another website, to show ads on a blog written in Bengali, the account will be revoked - and it's a lifetime revocation.<br />
<br />
And what ever language you write, the blog must have proper composition, grammar, and spelling.<br />
<br />
The minimum age for AdSense publishers is 18 years - partially because you need to have ability to write clearly, in your chosen language. Posts written by a pre teen are not accepted, for blogs hosting AdSense ads.<br />
<a name="PhotoVideo"></a><br />
<b>Photo / video blogs can't qualify.</b><br />
<br />
The crawler can't read photos. However intriguing or scenic a photo blog may be, it's not going to be approved, to host AdSense ads.<br />
<br />
You can include photos, on any suitable blog - but neither photos or videos can substitute for text.<br />
<br />
Neither AdSense or YouTube permit <a href="http://blogging.nitecruzr.net/2016/06/adsense-and-blogger-require-quality.html">ads on pages with YouTube content</a>, outside the YouTube website. Blogger blog posts, with YouTube videos not accompanied by substantial text content, will not display AdSense ads.<br />
<a name="JavaScript"></a><br />
<b>JavaScript based templates won't show ads.</b><br />
<br />
This is a known problem, with the <a href="http://blogging.nitecruzr.net/2015/11/adsense-does-not-work-with-dynamic.html">Blogger supplied dynamic templates</a>.<br />
<br />
Third party, JavaScript based templates will present a similar problem. Templates that provide <a href="http://blogging.nitecruzr.net/2015/04/use-dynamic-accessories-with-dynamic.html">numbered pages, and similar features</a>, are JavaScript based. Important post content, hidden behind JavaScript, cannot be read by the crawler.<br />
<br />
Similar to JavaScript based templates, some blog owners have added <a href="http://blogging.nitecruzr.net/2015/05/blogger-blogs-and-social-networking.html">"call to action" / social networking content</a> - JavaScript based popup windows, with "Like my blog!", "Subscribe to my blog!", and similar demands. Here, too, the AdSense crawler will be unable to read the blog.<br />
<a name="Temporary"></a><br />
<b>Ads may be displayed day by day - or week by week.</b><br />
<br />
Just because ads do not display today, that does not mean that they won't display tomorrow - or next week. Conversely, just because ads do display today, does not imply that they will be there tomorrow - or next week.<br />
<br />
Ads are displayed <a href="http://blogging.nitecruzr.net/2016/02/with-adsense-ads-are-not-based-on.html">when they are available</a>. If your blog shows ads for a given product this week, next week those ads may be discontinued - or they may be displayed on a more interesting or relevant blog.<br />
<a name="Subject"></a><br />
<b>Some blog subjects just won't qualify.</b><br />
<br />
AdSense explicitly <a href="https://support.google.com/adsense/answer/1348688" target="_blank">prohibits some blog subjects</a>. Other blog subjects, <a href="http://blogging.nitecruzr.net/search/label/AdSense%20Unwanted%20Content" target="_blank">even not prohibited</a>, are not compatible with the AdSense ecosystem - and blogs based on those subjects are unlikely to <a href="http://blogging.nitecruzr.net/2017/01/adsense-eligibility.html">ever display paying ads</a>.<br />
<br />
Crapola - blogs with lots of posts, of <a href="https://adsense.googleblog.com/2011/01/adsense-facts-fiction-part-v-unoriginal.html" target="_blank">unfocused subject and unoriginal content</a>, chosen simply to "bulk up" the blog - is not going to have paying ads. Ad managers, with any future, will only pay for blogs with a <a href="http://blogging.nitecruzr.net/2016/06/adsense-and-blogger-require-quality.html">consistent subject, and unique content</a>.<br />
<br />
<b>The bottom line.</b><br />
<br />
To host paying ads, <a href="http://blogging.nitecruzr.net/2016/06/adsense-and-blogger-require-quality.html">AdSense requires quality content</a>.<br />
<br />
If you want to host AdSense supplied ads, on your blog, you have to read and heed all <a href="https://support.google.com/adsense/answer/9724" target="_blank">AdSense Policies</a>. This is one more requirement, in <a href="http://blogging.nitecruzr.net/2015/10/how-to-activate-adsense-on-your-blog.html">activating ads on your blog</a>.<br />
<br />
And right now, some blog owners <a href="http://blogging.nitecruzr.net/2016/02/with-adsense-congratulations-is-only.html">may be receiving a congratulatory notice</a>, when approval is yet to be determined (or possibly, denied).<br />
<br />
---<br />
<br />
Some #Blogger blog owners want to use AdSense to make money with their blog - but they overlook the basic necessities of being an AdSense publisher. Besides the age / content volume issues which are easy enough to define, there is the need for AdSense to be able to properly choose ads to be shown on the blog.<br />
<br />
The AdSense crawler, which is a robotic process similar to any search engine, determines the ads to show - if it can crawl the blog and find useful details.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com2tag:blogger.com,1999:blog-24069595.post-49613965184574409322015-11-10T16:41:00.000-08:002016-01-23T07:36:03.624-08:00The "Next Blog" Link Is A Series Of CompromisesPeriodically, we see complaints about "Next Blog" content, in <a href="http://productforums.google.com/forum/?hl=en&fromgroups=#!categories/blogger/something-is-broken" target="_blank">Blogger Help Forum: Get Help with an Issue</a>.<blockquote>When I click on the "Next Blog" link, I get sent to blogs from many, many different languages. Can I set this to send me to primarily blogs published in English?</blockquote>or<blockquote>"Next Blog" sends me to blogs about "xxxxxxx". My blog is about "yyyyyyy". Why can't I get more blogs about "yyyyyyy"?</blockquote>What these blog owners do not understand is that using "Next Blog" involves compromise. <br />
<a name='more'></a><br />
Originally, "Next Blog" was simply a link to the most recently published blog. <br />
<br />
<b>"Next Blog" started out as a feature to encourage blog owners to publish.</b><br />
<br />
"Next Blog" was, long ago, a tool that <a href="http://blogging.nitecruzr.net/2008/01/more-traffic-to-our-blogs.html">encouraged blog publishing</a>. Anybody clicking on "Next Blog" was sent to the most recently published blog - based on links in the "Recently Updated Blogs" list. <br />
<br />
"<a href="http://blogging.nitecruzr.net/2006/08/polling-blogger.html">Recently Updated Blogs</a>" was a rolling list of the immediately previous 10 minutes of blog updates - which was observed to contain anywhere from 4,000 - 8,000 entries. At an average of 6,000 entries in 10 minutes, this gave each published blog .1 second of fame. <br />
<br />
Anybody clicking on "Next Blog" was sent to the blog at the top of "Recently Updated Blogs" - which would generally be the blog updated in the most recent .1 second of time. <br />
<br />
<b>The blogs published more often would get more "Next Blog" traffic.</b><br />
<br />
Blogs that were published more often ended up at the top of the list more - and got more readers, surfing "Next Blog". This became a great motivation factor, for publishing - based on such a simple concept. <br />
<br />
<b>Spammers found how to use "Next Blog" to get traffic to their blogs.</b><br />
<br />
Then spammers found out about "Next Blog", by observing the referer link in any visitor log. They started publishing blogs in mass quantity, simply to <a href="http://blogging.nitecruzr.net/2014/04/spammers-and-content-risk-management.html">collect readers, and send them to payload blogs</a> - filled with hacking, porn, and / or spam. <br />
<br />
Eventually, Blogger <a href="http://blogging.nitecruzr.net/2014/01/the-recently-updated-blogs-display-is.html">stopped using "Recently Updated Blogs"</a>, as the sole referring factor. Based on suggestions from many blog owners, they now analyse blogs based on multiple factors - such as geographical location, language, and subject - and <a href="http://blogging.nitecruzr.net/2010/05/your-blog-content-and-your-next-blog.html">match the blog currently visible in the browser</a>, with blogs targeted by "Next Blog". <br />
<br />
<b>All subjects, in all languages and locations, are not uniformly popular.</b><br />
<br />
Unfortunately, the matching concept - popular though it should be - is not uniformly applicable. Consider how many blogs might be published, about recipes, in English, in New York City. Will there be the same number of blogs about nuclear physics, in Greek, in London? <br />
<br />
Greek nuclear physicists, in London, would have a minimal number of similar blogs - and would be more likely to see the same group of blogs, over and over. English housewives in New York City, on the other hand, would have a rich neighbourhood of blogs to read. <br />
<br />
And that's reality. If you live in New York City, and want recipes in English, you're likely to see a non ending cornucopia of blogs, constantly updated. If you live in London, and want blogs in Greek about nuclear physics, you're going to see a smaller number of different blogs, updated less frequently. <br />
<br />
If you surf "Next Blog", and see blogs written in a "foreign" language, about subjects that don't interest you, seldom updated, <a href="http://blogging.nitecruzr.net/2010/10/new-next-blog-link-is-lame-because.html">try to not blame Google</a>, exclusively. There won't ever be the same number of blogs in every language, published as often, from every city worldwide, about every different subject.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-62875690427498082372015-05-30T14:49:00.002-07:002015-06-23T16:52:15.537-07:00Scheduled Posts - The Challenge ContinuesOne Blogger feature, that is occasionally mentioned in <a href="http://productforums.google.com/forum/?hl=en&fromgroups=#!categories/blogger/something-is-broken" target="_blank">Blogger Help Forum: Get Help with an Issue</a>, is the issue of scheduling post publication.
<br /><br />
Setting up a scheduled post is extremely simple - and that may be part of the problem. Before you publish a post, you give the post a published date / time that occurs in the future. The post date / time becomes the scheduled posting date / time.
<br /><br />
And there is where one possible problem, with scheduled posts, may start. Long ago, when scheduled posts were first introduced, the wizard for setting the date and time was rather simple.
<br /><br />
Since this is a new post, I can look under "Post settings", to the right, and see the "Schedule" option. If I expand "Schedule", I can see the selected default of "Automatic". If I select "Set date and time", the fun begins.
<br /><a name='more'></a><br />
Do you see the clever GUI design, in the "Schedule" wizard - as it is, <a href="#Today">right now</a>?
<br /><a name="Simple"></a><br /><b>The date / time wizard, when Schedule Posts was first introduced, was very simple.</b><br />
When the Scheduled Posts feature was first introduced, "Date" and "Time" was simply two empty boxes, with no hint of what to put into the boxes. Add to that the certainty that some people <a href="http://blogging.nitecruzr.net/2011/01/world-wide-blogger-culture-and-date.html">might enter either the date or time "wrong"</a>, and you would get oddities.<ul><li>Posts scheduled for future publication, when intentionally backdated.</li><li>Posts published immediately, with back dates, when intentionally scheduled for future publication.</li><li>Posts scheduled, but at the "wrong" time.</li><li>Posts that never published, because the publish date / time was far in the future.</li><li>Now that you see the problem, I bet you can think of more scenarios.</li></ul>
<br /><b>Blogger fixed the first identified problems - and caused new problems.</b><br />
After we identified <a href="http://blogging.nitecruzr.net/2011/01/world-wide-blogger-culture-and-date.html">the possible problems with scheduled posts</a>, Blogger removed the date box, and replaced it with the calendar. This forced people to see and set the date, using the calendar display.
<br /><br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjhaCX109xr8p3QdoOpuL-1s3yihzA5rSAbBNoizU85uybAdCHuzt43T9qg0CrybLWBiYBhJgwazn4j_gKklhh0j9S8FtJBBVtiQnelCNTegeueq5Zl6zv2fRZ50Gvg-wnwUwNyfw/s1600/Screenshot+2015-05-30+at+14.56.01.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjhaCX109xr8p3QdoOpuL-1s3yihzA5rSAbBNoizU85uybAdCHuzt43T9qg0CrybLWBiYBhJgwazn4j_gKklhh0j9S8FtJBBVtiQnelCNTegeueq5Zl6zv2fRZ50Gvg-wnwUwNyfw/s320/Screenshot+2015-05-30+at+14.56.01.png" /></a><br />If you can read a calendar, you can set the month correctly.<br /><br />But - does that solve the problem?<br clear=left />
<br /><br />
The calendar selected date worked great, for posts back or forward dated only a few days or weeks. You could select any date in the current month - or page backwards or forwards a month or two, and select a date. And the problem with people entering the date "wrong" was solved, with everybody able to see the month, and select a day.
<br /><br /><b>Everybody did not appreciate the solution.</b><br />
The calendar did not please everybody. People who had to <a href="http://blogging.nitecruzr.net/2012/06/world-wide-blogger-culture-and-date.html">change the date more than a month or two</a> complained, because they had to sit there and click - click - click one month at a time, to select a month far in the past or future.
<br /><a name="Today"></a><br /><b>Blogger then tried what we have, today.</b><br />
So Blogger created a hybrid wizard - the date and time are both type in fields - and the date can be selected using a calendar. And when the date is typed. the calendar changes, to indicate the month typed.
<br /><br />
Does everybody, typing in the date, to schedule post publication, always look at the calendar - or the resulting Schedule date / time?
<br /><br /><b>This is the current date / time wizard.</b><br /><br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_QgLMx4x1rPeV9BUV-6Ay78KAM0E70kjzMUKpZ-DHHWxJACGuXTZ21pqXcYDPrra4VZC2O-ZUHIjI7V9ATp_D3or9ElYYESMUS0G2uDE2bjQWoiemAiRe7dSWznuGpKnghVNW2w/s1600/Screenshot+2015-05-30+at+15.42.28.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_QgLMx4x1rPeV9BUV-6Ay78KAM0E70kjzMUKpZ-DHHWxJACGuXTZ21pqXcYDPrra4VZC2O-ZUHIjI7V9ATp_D3or9ElYYESMUS0G2uDE2bjQWoiemAiRe7dSWznuGpKnghVNW2w/s320/Screenshot+2015-05-30+at+15.42.28.png" /></a><br />How can this not work?<br /><br />See below, for discussion.<br clear=left />
We have type in fields for date, and for time - and below that, the months calendar, with "today" highlighted - and controls, to select the previous or next month.
<br /><br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgL_wJeMLw7znbhzTDEY2rEtN-saBPCXBFan-Nj33aXevKTtW_7ixM8yRiDGEHTDOZrMjytLihoV1_6aE00RQGFRP97ALb9F_u4aOEG163j6jnYyWU-boOUqu3j9vpFcDyVlQHKIA/s1600/Screenshot+2015-05-30+at+15.58.07.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgL_wJeMLw7znbhzTDEY2rEtN-saBPCXBFan-Nj33aXevKTtW_7ixM8yRiDGEHTDOZrMjytLihoV1_6aE00RQGFRP97ALb9F_u4aOEG163j6jnYyWU-boOUqu3j9vpFcDyVlQHKIA/s320/Screenshot+2015-05-30+at+15.58.07.png" /></a><br />It's now 4:00 PM. Why do we still see "2:49 PM"?<br clear=left />
My suspicion is that some people who type in the date may make a mistake - and not always catch the mistake. I'll also bet that this problem exists, in larger volume than is reported - but only a few people see it. Most people use post scheduling as a convenience. How many schedule a post, then stick around to watch it publish?
<br /><br />
You compose your post, you schedule your post - then you're gone. You come back, sometime later, and it's published. Do you know, for a fact, that it published on the second - or the date - scheduled?
<br /><br />
I'm also wondering how scheduled posts are published, in general - but that may be a subject for another post, later. Right now, the question is how to ensure post schedule dates can be accurately typed, to eliminate misscheduled posts.
<br /><br />
And besides people who don't enter date / time correctly, there's people who <a href="http://blogging.nitecruzr.net/2015/06/press-publish-to-schedule-post-to.html">never think to hit "Publish"</a> - then watch as "scheduled" publication time comes and goes, with the post still in Draft state.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com2tag:blogger.com,1999:blog-24069595.post-46427315527582269672015-05-27T16:58:00.000-07:002016-02-19T17:46:17.334-08:00Non English Language Blogs, And Abuse ReviewWith Blogger blogs becoming more popular in countries where English is not the native language, we've seen a lot of blogs classified as spam - both righteously, and spuriously. <br />
<br />
Most spam reviews, originally, involved blogs with commercial spam - excessive advertisements, with little subject content. As the focus of spam classification shifted to blogs with content, we've been seeing more <a href="http://blogging.nitecruzr.net/2015/02/what-is-difference-between-copying-and.html">non commercial classifications</a> - large blogs with unfocused subjects, and content scraped or syndicated. <br />
<br />
Combining the two trends - more blogs in non English languages, and spam classifications which focus on non commercial content, we see blogs which require more people to review. And the people required need familiarity with the languages, and the subjects, of the blogs which need review. <br />
<a name='more'></a><br />
As an expert helper in Blogger Help Forums, I've seen a lot of trends, among the spam review requests, started in <a href="http://productforums.google.com/forum/?hl=en&fromgroups=#!categories/blogger/something-is-broken" target="_blank">Blogger Help Forum: Get Help with an Issue</a>. <br />
<br />
<b>Blogs written in English are not difficult to review.</b><br />
With non commercial spam, and <a href="http://blogging.nitecruzr.net/2009/11/attack-of-clones.html">large blogs full of non focused content, or scraped / syndicated content</a>, which are published in English, Google is truly your friend. <br />
<br />
It is not difficult to identify blogs that are righteously, or spuriously, classified. Nor is it difficult to identify which blogs are classified for commercial content vs non commercial content. <br />
<br />
<b>Blogs not written in English will present some challenge.</b><br />
Blogs which are not written in English, however, are going to be a challenge - both in the initial forum <a href="http://blogging.nitecruzr.net/2015/01/spam-review-requires-triage.html">problem discussion triage</a>, and the later Blogger Policy Review final review. <br />
<br />
Identifying the blog subject requires familiarity with the blog language, and with the blog subject. And identifying scraped / syndicated content, or reviewing for "objectionable" content, requires ability to at least read the content - then to run the content through Google Search, possibly in multiple languages. <br />
<br />
<b>Google will have even more of a challenge, with non English blogs.</b><br />
Google can automate much of the initial abuse classification - in every language. Blogs which later require manual review will require a human being to sort through the content - and the human will need language and subject familiarity. <br />
<br />
As the automated abuse / objectionable content classification process becomes more reliable, some blogs will require manual review after they are classified (righteously, or spuriously), for more subtle content / TOS violations. All of this creates demands, when review is needed.<br />
<br />
<div style="background-color: white;"><ul><li>Ability to judge abuse / content, in general.</li>
<li>Ability to judge abuse / content, in subtle details.</li>
<li>Familiarity with the blog language.</li>
<li>Familiarity with the blog subject / cultural issues.</li>
<li>Diversity and size of the blog.</li>
</ul></div><br />
All of these details will be relevant, when answering the question, asked by many blog owners.<blockquote>How long will I have to wait, before my blog is restored / reviewed?</blockquote>Some blog owners will wait, with eventual reward; and <a href="http://blogging.nitecruzr.net/2009/10/waiting-for-tap-on-shoulder.html">others may wait forever</a>. And the owners of blogs published in obscure non English languages / relevant to non mainstream cultures will wait longer, as Google expands the cultural and linguistic diversity of the Blogger Policy Review team, to reflect world diversity. <br />
<br />
<b>Spammer activity will follow cultural / linguistic diversity, in Blogger.</b><br />
There are over 300 languages in the world, with Blogger currently supporting 62 languages in <a href="http://blogging.nitecruzr.net/2007/04/make-your-blog-speak-your-language.html">the dashboard Language setting</a>. As Blogger expands its linguistic diversity, spammer activity will surely follow. <br />
<br />
Spammers will both conceal abusive activity, and target victims, using blogs published in obscure languages. It's possible that blogs published in obscure languages will be less subject to spam classification processes. <br />
<br />
The Blogger Policy Review team will have to expand, similarly - if they hope to reliably support <a href="https://productforums.google.com/forum/preview/#!topic/blogger/hdxqip_nanA;context-place=forum/blogger" target="_blank">requested spam review</a>, using human beings. And as Blogger blogs become more popular in countries where English is not common, blog owners <a href="http://blogging.nitecruzr.net/2015/06/content-spam-classification-has-two.html">have to be more patient</a>, when their blogs are (righteously, or spuriously) classified as objectionable content / suspected spam hosts.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-5870937982947192642015-05-23T14:43:00.000-07:002018-02-18T04:26:37.849-08:00Publish A Language Related Blog ClusterAs Blogger blogs become more popular outside the U.S.A., we see various blog owners who are multi-lingual - and who want to publish simultaneously, in multiple languages. <br />
<br />
We see the question, occasionally in <a href="http://productforums.google.com/forum/?hl=en&fromgroups=#!categories/blogger/how-do-i" target="_blank">Blogger Help Forum: Learn More About Blogger</a>.<blockquote>How do I publish my blog in English, French, and Spanish - and keep a good relationship with my readers, the search engines, and the anti spam bots?</blockquote>This is not difficult to do - just publish a well balanced and linked blog cluster, with the "hreflang" tag defining the related blogs, to the search engines. <br />
<a name='more'></a><br />
Publishing a multi-language blog cluster is not difficult.<ol><li>Choose a blog name, that lets you publish, and lets your readers identify, the blogs.</li>
<li>Publish each blog, in its own specific language.</li>
<li>Combine and link the blogs, as a cluster.</li>
<li>Identify the members of the cluster, to the search engines.</li>
</ol><br />
<b>Choose a blog name, that lets you publish, and lets your readers identify, the blogs.</b><br />
<br />
You'll want a blog name that indicates how each blog is part of a set of blogs, yet differs from the others. You'll need a name that's consistently available (you can't publish a URL that's already being used), and describes the relationship of each blog, to the others. <br />
<br />
If I was tri-lingual, I could publish this blog in <a href="http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes" target="_blank">English, French, and Spanish</a>. I could publish to BlogSpot.<ul><li>en-blogging-nitecruzr.blogspot.com</li>
<li>es-blogging-nitecruzr.blogspot.com</li>
<li>fr-blogging-nitecruzr.blogspot.com</li>
</ul>and maybe, later, to a custom domain.<ul><li>en.blogging.nitecruzr.net</li>
<li>es.blogging.nitecruzr.net</li>
<li>fr.blogging.nitecruzr.net</li>
</ul><br />
<b>Publish each blog, in its own specific language.</b><br />
<br />
Each blog, published in a non English language, needs <a href="http://blogging.nitecruzr.net/2009/11/multi-lingual-blogging-requires.html">the proper Language setting</a>. This helps you publish each blog, using the post editor, more consistently - and it helps the search engines index the blogs properly.<br />
<br />
<b>AdSense will only supply ads for supported languages.</b><br />
<br />
If you want AdSense to supply ads on your blogs, you will have to <a href="https://support.google.com/adsense/answer/9727" target="_blank">publish in languages supported by AdSense</a>. "hreflang" won't change that. You will need a real, human audience, for all blogs.<br />
<br />
<b>Publish each blog - and translate the material - yourself.</b><br />
<br />
Don't use Google Translator, to produce translated blogs. Neither the search engines, nor AdSense, will crawl <a href="http://blogging.nitecruzr.net/2015/11/adsense-does-not-work-with-dynamic.html">a blog that uses JavaScript, to display content</a>. You will have to do all of the work.<br />
<br />
<b>Combine and link the blogs, as a cluster.</b><br />
<br />
There are a number of techniques that you can use, to <a href="http://blogging.nitecruzr.net/2008/04/separate-your-blogs-yet-keep-them.html">make a blog cluster</a> that is appealing - and functional - to your readers. Combining and linking each blog to the others, yet keeping each blog different from the others, can use <a href="http://blogging.nitecruzr.net/2007/06/adding-your-blogger-blog-to-your-non.html">a variety of Blogger features and options</a>. <br />
<br />
<b>Identify the members of the cluster, to the search engines.</b><br />
<br />
Besides the Language settings to identify indexing characteristics of each different blog, you'll want to <a href="http://blogging.nitecruzr.net/2015/05/hreflang-and-language-region-based-blog.html">use the "hreflang" tag</a>, to indicate which blogs are related. The search engines will index the blogs as a set - and be able to distinguish between the blogs properly. <br />
<br />
<b>The end result will be pleasing to your readers - and to the search engines.</b><br />
<br />
When you're done, you'll end up with <a href="https://productforums.google.com/forum/#!category-topic/blogger/T4oa4Vf-cY8" target="_blank">a set of blogs</a> that help your readers enjoy what you have to say - and help the search engines index each blog properly. And that will lead to more readers - and possibly another language to learn and publish.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-69193304657295406202015-05-10T12:51:00.000-07:002017-04-21T22:51:54.006-07:00"hreflang", And Language / Region Based Blog SetsIf you publish a set of blogs in multiple languages, or customised for different geographical regions, you may have concerns about search engine reputation, and / or spurious spam classification. <br />
<br />
Blog sets which are legitimately replicated, for either different languages or geographical regions, have been known to be caught in <a href="http://blogging.nitecruzr.net/2009/11/attack-of-clones.html">the infamous Blogger spam trap</a>. And blogs which contain duplicated content can be a problem, both in Blogger and in Google Search. <br />
<br />
Google provides a tag, which lets you indicate, to Blogger and to the search engines, blogs that are members of a legitimate blog set. <br />
<a name='more'></a><br />
Blogs in sets, which are based on either language or region, can be identified using <a href="https://support.google.com/webmasters/answer/189077?hl=en" target="_blank">the "hreflang" tag</a>. <br />
<br />
<b>The "hreflang" tag lets you identify legitimate blogs that relate to each other.</b><br />
<br />
This tag will only work with existing blogs - and it will work best with blogs that are intentionally and genuinely related - by either language or geographical region. It won't simply create aliases of an existing blog - but it will let you identify <a href="http://blogging.nitecruzr.net/2008/04/separate-your-blogs-yet-keep-them.html">blogs which are related</a>, and which may contain similar material. <br />
<br />
The tags are based on codes provided by the <a href="http://en.wikipedia.org/wiki/International_Organization_for_Standardization" target="_blank">International Organization for Standardization</a> - they are not fictitious or imaginative. The URLs of the blogs, in the set, are your choice - the ISO codes, used in the tags, are not your choice. <br />
<br />
<b>I could publish an English / French / Spanish set.</b><br />
<br />
If I was multi-lingual (for the record, I'm not), I could publish this blog in <a href="http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes" target="_blank">English, French, and Spanish</a>.<br />
<br />
<ul><li>blogging-en.nitecruzr.net ("en" = ISO code for "English")</li>
<li>blogging-es.nitecruzr.net ("es" = ISO code for "Spanish")</li>
<li>blogging-fr.nitecruzr.net ("fr" = ISO code for "French")</li>
</ul><br />
or maybe<br />
<br />
<ul><li>en.blogging.nitecruzr.net</li>
<li>es.blogging.nitecruzr.net</li>
<li>fr.blogging.nitecruzr.net</li>
</ul><br />
In the template header, for each blog, I would add <br />
<br />
<blockquote><link rel="alternate" hreflang="en" href="http://blogging-en.nitecruzr.net/" /><br />
<link rel="alternate" hreflang="es" href="http://blogging-es.nitecruzr.net/" /><br />
<link rel="alternate" hreflang="fr" href="http://blogging-fr.nitecruzr.net/" /><br />
</blockquote><br />
or maybe <br />
<br />
<blockquote><link rel="alternate" hreflang="en" href="http://en.blogging.nitecruzr.net/" /><br />
<link rel="alternate" hreflang="es" href="http://es.blogging.nitecruzr.net/" /><br />
<link rel="alternate" hreflang="fr" href="http://fr.blogging.nitecruzr.net/" /><br />
</blockquote><br />
or even <br />
<br />
<blockquote><link rel="alternate" hreflang="en" href="http://en-blogging-nitecruzr.blogspot.com/" /><br />
<link rel="alternate" hreflang="es" href="http://es-blogging-nitecruzr.blogspot.com/" /><br />
<link rel="alternate" hreflang="fr" href="http://fr-blogging-nitecruzr.blogspot.com/" /><br />
</blockquote><br />
<b>I could publish an Australia / Canada / Great Britain / USA set.</b><br />
<br />
Similarly, if I wanted to publish <a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Current_codes" target="_blank">"Australia", "Canada", "Great Britain", and "USA"</a> regional versions of this blog (all regional dialects of "English"), I might have<br />
<br />
<blockquote><link rel="alternate" hreflang="en-au" href="http://blogging-au.nitecruzr.net/" /><br />
<link rel="alternate" hreflang="en-ca" href="http://blogging-ca.nitecruzr.net/" /><br />
<link rel="alternate" hreflang="en-gb" href="http://blogging-gb.nitecruzr.net/" /><br />
<link rel="alternate" hreflang="en-us" href="http://blogging-us.nitecruzr.net/" /><br />
</blockquote><br />
or maybe <br />
<br />
<blockquote><link rel="alternate" hreflang="en-au" href="http://au.blogging.nitecruzr.net/" /><br />
<link rel="alternate" hreflang="en-ca" href="http://ca.blogging.nitecruzr.net/" /><br />
<link rel="alternate" hreflang="en-gb" href="http://gb.blogging.nitecruzr.net/" /><br />
<link rel="alternate" hreflang="en-us" href="http://us.blogging.nitecruzr.net/" /><br />
</blockquote><br />
or even <br />
<br />
<pre><blockquote><span style="background-color: white;">
<link rel="alternate" hreflang="en-au" href="http://au-blogging-nitecruzr.blogspot.com/" />
<link rel="alternate" hreflang="en-ca" href="http://ca-blogging-nitecruzr.blogspot.com/" />
<link rel="alternate" hreflang="en-gb" href="http://gb-blogging-nitecruzr.blogspot.com/" />
<link rel="alternate" hreflang="en-us" href="http://us-blogging-nitecruzr.blogspot.com/" />
</span></blockquote></pre><br />
<b>All blogs must be real - and must be maintained as any other blog.</b><br />
<br />
Again, each blog must exist, as referenced - and each blog should be published, in equal activity to the others, for best results. It's similar to getting the best performance for your (gasoline powered) internal combustion engine driven automobile. All cylinders must operate, in the right sequence and timing.<br />
<br />
The "hreflang" tag won't create logical aliases - nor will it let you blatantly publish duplicated content, or compensate for blogs with no posting activity. You will need legitimate blogs, with <a href="http://blogging.nitecruzr.net/2013/12/blogger-blog-content-needs-to-be-unique.html">genuinely relevant and unique content</a> - each relevant within itself, and in comparison to the other blogs in the set. <br />
<br />
If you are prepared to publish <a href="http://blogging.nitecruzr.net/2015/05/publish-language-related-blog-cluster.html">legitimate blogs in a set</a>, however, the "hreflang" tag will let you do that - and it should decrease the possibility of bogus spam classification, and duplicated content penalties. And you have one more way to <a href="http://blogging.nitecruzr.net/2007/06/adding-your-blogger-blog-to-your-non.html">combine blogs, in clusters</a>.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-74870928306570180182015-04-12T18:32:00.000-07:002018-07-03T19:55:09.958-07:00European Residents And EU Cookie ComplianceBlog owners who live in Europe have <a href="http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm" target="_blank">a recently added regulation</a> with which you need to comply.
<br /><br />
If you publish a blog, and host AdSense ads, you already have part of the requirement - the properly written Cookie Advisory. If you live in Europe, and view this blog, chances are that you have been offered the chance to view the <a href="http://blogging.nitecruzr.net/p/privacy-policy.html" target="_blank">Nitecruzr.Net Privacy Policy</a>, which includes my Cookie Advisory.
<br /><br />
If your blog displays the Blogger Navbar, you have a compliant Cookie Advisory Banner which is provided by Blogger, in the navbar. If you have <a href="http://blogging.nitecruzr.net/2015/03/disable-enable-navbar-on-your-blog.html">disabled the navbar</a> - or if the blog uses a dynamic template (and has no navbar), you can add a Cookie Advisory Banner as supplied by Google Cookie Choices.
<br /><a name='more'></a><br />
The simplest solution, for cookie advisory compliance, to display a cookie advisory, is to <a href="http://blogging.nitecruzr.net/2015/03/disable-enable-navbar-on-your-blog.html">enable the navbar</a>.
<br /><br />
If you choose to leave the navbar disabled on your blog - or if your blog has no navbar because it uses a dynamic template - you will need <a href="https://www.cookiechoices.org/" target="_blank">the Google Cookie Choices Notification Bar</a>. The Notification Bar has 2 components.<ul><li>"cookiechoices.js"</li><li>The Cookie Choices Notification Bar code</li></ul>
<br /><br />
First, download "<a href="https://www.cookiechoices.org/cookiechoices.zip" target="_blank">cookiechoices.zip</a>", unzip it, and upload "cookiechoices.js" to a <a href="http://blogging.nitecruzr.net/2014/11/adding-office-document-to-your-blog.html">Google Docs, Google Drive</a>, or Google Sites folder.
<br /><br />
Next, modify the Notification Bar code, to match your blog.
<pre>
<script src="<span style="background-color: yellow;">cookiechoices.js</span>"></script>
<script>
document.addEventListener('DOMContentLoaded', function(event) {
cookieChoices.showCookieConsentBar('<span style="background-color: yellow;">message for visitors</span>',
'<span style="background-color: orange;">close message</span>', '<span style="background-color: orange;">learn more</span>', '<span style="background-color: yellow;">http://example.com</span>');
});
</script>
</pre>
<br /><br />
You should customise the sections of code, as appropriate for your blog.<ul><li>"<span style="background-color: yellow;">cookiechoices.js</span>" Indicate the URL of your Google Docs, Google Drive, or Google Sites file which contains the code, as uploaded.</li><li>'<span style="background-color: yellow;">message for visitors</span>' This provides the advice, immediately displayed in the banner.</li><li>'<span style="background-color: yellow;">http://example.com</span>' This provides detail advice, in a separate file.</li></ul>You may, if you wish, customise the captions<ul><li>'<span style="background-color: orange;">close message</span>'</li><li>'<span style="background-color: orange;">learn more</span>'</li></ul>This lets you make your banner more relevant to your readers.
<br /><br />
<pre>
<script src="<span style="background-color: yellow;">cookiechoices.js</span>"></script>
<script>
document.addEventListener('DOMContentLoaded', function(event) {
cookieChoices.showCookieConsentBar('<span style="background-color: yellow;">This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies.</span>',
'<span style="background-color: orange;">Close message ...</span>', '<span style="background-color: orange;">Learn more ...</span>', '<span style="background-color: yellow;">http://blogging.nitecruzr.net/p/privacy-policy.html</span>');
});
</script>
</pre>
<br /><br />
Having customised your Notification Bar code, use the dashboard <a href="http://blogging.nitecruzr.net/2010/03/editing-blog-template.html">Template "Edit HTML"</a> wizard, and add it to your template. The current recommendation appears to be just above the "</body>" tag.
<br /><br />
<pre>
<script src="<span style="background-color: yellow;">cookiechoices.js</span>"></script>
<script>
document.addEventListener('DOMContentLoaded', function(event) {
cookieChoices.showCookieConsentBar('<span style="background-color: yellow;">Welcome to Blogging Dot Nitecruzr Dot Net! This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies.</span>',
'<span style="background-color: orange;">Thanks! I understand.</span>', '<span style="background-color: orange;">I'd like more information!</span>', '<span style="background-color: yellow;">http://blogging.nitecruzr.net/p/privacy-policy.html</span>');
});
</script>
</body>
</pre>And Save changes.
<br /><br />
Please, as always, <a href="http://blogging.nitecruzr.net/2008/02/backup-your-layouts-template.html">backup the template</a> - before and after adding the code.
<br /><br />
Each blog reader, with <a href="http://blogging.nitecruzr.net/2010/11/enabling-cookies-and-scripts-in-your.html">third party cookies</a> properly enabled, will see the Advisory Banner only once (having hit '<span style="background-color: orange;">Thanks! I understand.</span>'). If they have third party cookies blocked - or if they clear cookies, they will see the Banner again.
<hr /><span style="color: red;"><b>(Update 8/1/2015):</b></span> Blogger has provided their own automatic version of CookieChoices, which requires only <a href="http://blogging.nitecruzr.net/2015/08/eu-cookie-compliance-july-2015.html">verification, for many blogs</a>.<hr />Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com2tag:blogger.com,1999:blog-24069595.post-15276445008468630642015-02-15T18:03:00.000-08:002015-04-08T10:01:56.060-07:00Don't Confuse Simplicity, And Easy InstallationOne naive attitude, about publishing a Blogger blog, involves adding features to one's blog - and the observation that every Blogger feature or modification is not uniformly available, with entry level instructions.
<br /><br />
We see the complaints, in <a href="http://productforums.google.com/forum/?hl=en&fromgroups=#!categories/blogger/something-is-broken" target="_blank">Blogger Help Forum: Get Help with an Issue</a>, too frequently.<blockquote>I can't get this feature to work! Why is Blogger so complicated?</blockquote>and<blockquote>I have no idea what I need to do. Please guide me, in simple language - as if I were 6 years old!</blockquote>Both attitudes show lack of understanding about technical projects in general - and Blogger features, and modifications, in particular.
<br /><a name='more'></a><br />
Just because Blogger help documentation is written in English - and various other languages - and many Blogger features are easy to use - this won't mean that every possible Blogger feature will be equally well designed and documented.
<br /><br />
Even when your neighbour has setup a blog <a href="http://blogging.nitecruzr.net/2009/02/your-neighbours-cough.html">with a given feature</a>, that does not mean that <a href="http://blogging.nitecruzr.net/2014/12/design-your-blog-as-you-develop-your.html">your blog requires that same feature</a> to be installed - before you publish, with some content. And even if the feature of your choice is truly useful, for your blog, please don't complain if the documentation provided is not completely understandable, to you.
<br /><br />
Some Blogger features require some <a href="http://blogging.nitecruzr.net/2013/03/when-you-setup-custom-domain-please.html">background experience with Blogger</a> - and even with <a href="http://blogging.nitecruzr.net/2007/06/you-have-to-speak-language.html">technical principles in general</a>.
<br /><br />
If the process of getting the feature of your choice installed, or working, on your blog, is unsuccessful, please don't complain<blockquote>Blogger is so easy to use. Why do some features require geek speak?</blockquote>Much of Blogger is easy to use, because of incredibly complicated background system design.
<br /><br />
Many features are not at all simple, in reality. What you see, on your blog or in the template, may be <a href="http://blogging.nitecruzr.net/2013/02/deleted-locked-blogs-have-several.html">just a tiny iceberg tip</a>.
<br /><br />
Some Blogger features will always require <a href="http://blogging.nitecruzr.net/2007/04/your-computer-and-blogger.html">some blog owners</a> to do some research, and read more documentation. Please, don't demand help.<blockquote>I don't speak techie! Please explain this to me, as if I were a six year old!!</blockquote>You may have to accept some issues as your responsibility, and politely accept the advice provided. And then, <a href="https://productforums.google.com/d/topic/blogger/FOu4cDIhwuA/discussion" target="_blank">read the articles</a> behind the links.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com1tag:blogger.com,1999:blog-24069595.post-76157636834243589242015-02-08T20:40:00.000-08:002015-04-08T10:01:56.428-07:00Avoid "Next Blog" FixationWe see occasional reports in <a href="http://productforums.google.com/forum/?hl=en&fromgroups=#!categories/blogger/something-is-broken" target="_blank">Blogger Help Forum: Get Help with an Issue</a>, about the "Next Blog" link in the navbar, and undesirable behaviour.
<br /><br />
Long ago, "Next Blog" was used to link to the most recently published blogs, to encourage blog publishing, using <a href="http://blogging.nitecruzr.net/2014/01/the-recently-updated-blogs-display-is.html">the now dead "Recently Updated Blogs" database</a>. Since multiple Blogger blogs are published each second, this gave a pseudo random effect to "Next Blog".
<br /><br />
Blog owners disliked the pseudo random effect. Some wanted to view blogs only published in their language, others wanted blogs geographically similar - and some demanded relevant subjects.
<br /><br />
The pseudo random effect was abused by spammers, who would setup <a href="http://blogging.nitecruzr.net/2009/11/attack-of-clones.html">spam blog farms</a>, then publish each spam blog repeatedly, to attract victims. "Next Blog" hacking was a popular spammer technique.
<br /><a name='more'></a><br />
In an effort to reduce the spam - and to make the "Next Blog" link relevant by geography, language, and subject, Blogger developed <a href="http://blogging.nitecruzr.net/2010/05/your-blog-content-and-your-next-blog.html">"Next Blog" relevance</a>.
<br /><br />
When you hit "Next Blog" now, a Blogger script analyses the blog which you are currently viewing - and attempts to identify similar blogs. The script then randomly picks a blog from the "similar" collection, for viewing.
<br /><br />
The "similar" collection has to be fuzzy - and requires compromise. All blogs will not necessarily have large collections of other blogs similar in geographical location, in language, and in subject matter simultaneously. In some cases, a "Next Blog" viewer may be forced to view a blog which is irrelevant in geography, language, and / or subject.
<br /><br />
In extreme cases, a "Next Blog" viewer may end up viewing a very limited group of blogs. Repeatedly hitting "Next Blog" may display one or more blogs repeatedly. With a small enough collection of similar blogs, "Next Blog" may appear fixated, and display the same set of similar blogs, repeatedly.
<br /><br />
To avoid "Next Blog" fixation, a viewer may need to start from a different blog before hitting "Next Blog", and after <a href="http://blogging.nitecruzr.net/2010/11/clearing-cache-cookies-and.html">clearing cache, cookies, and sessions</a>, and restarting the browser. This will reset the "Next Blog" relevance database for the user - and provide a new, and hopefully more diverse, set of similar blogs for viewing.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-20950438523863912052015-01-05T12:11:00.000-08:002017-12-23T20:04:33.068-08:00Inviting Comments To Your Blog Is Not Cut And DriedBlog owners are periodically asking themselves<blockquote>How do I invite my readers to leave comments?</blockquote>Some blog owners think of commenting as the most important way to get new readers. <br />
<br />
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. <br />
<a name='more'></a><br />
<b>Variations</b><br />
There are four comment form placement options, for Blogger blogs.<ol><li>Embedded.</li>
<li>Full page.</li>
<li>Pop up window.</li>
<li>Dynamic template.</li>
</ol>There are two display contexts.<ol><li>Index page view (archive retrieval, label search, main page).</li>
<li>Post page view.</li>
</ol>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" <a href="http://blogging.nitecruzr.net/2010/12/show-setting-in-settings-formatting.html">will only apply to main page view</a>. And main page display with only one post displayed, without jump break, will still be index page view.<br />
<br />
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" <a href="http://blogging.nitecruzr.net/2010/12/show-setting-in-settings-formatting.html">will only apply to main page view</a>. And main page display with only one post displayed, without jump break, will still be index page view.<br />
<br />
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<blockquote>Please, leave a comment!</blockquote>That simple invitation can vary according to the the nationality of the blog owner, and to the nature of the blog. <br />
<br />
<b>Blog Language</b><br />
Comments is an English word. Every blog that's published in a non English language has a different word for "comments".<ul><li>en français: commentaires.</li>
<li>in italiano: commenti.</li>
<li>en español: comentarios.</li>
</ul>And some languages phrase plurals significantly.<ul><li>0 comments.</li>
<li>1 comment.</li>
<li>2 comments.</li>
</ul>Very few blog owners publish a blog in (USA) English, and want the blog captioned with "1 comments", or "2 comment". <br />
<br />
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!". <br />
<br />
<b>Blog Nature</b><br />
Then, some blog owners don't like the word "comments", they feel that the word should be changed, to <a href="http://blogging.nitecruzr.net/2012/05/setting-options-in-post-template.html">reflect the nature of their blog</a>. 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). <br />
<br />
<b>Form Placement</b><br />
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 <a href="http://blogging.nitecruzr.net/2009/05/embedded-comments-and-main-page-view.html">all comment placement options</a>, 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. <br />
<br />
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. <br />
<br />
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 <a href="http://blogging.nitecruzr.net/2014/12/confusion-from-comments-and-captcha.html">the hated CAPTCHA form</a>. <br />
<br />
<b>The Reader's Language</b><br />
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 <a href="http://blogging.nitecruzr.net/2009/06/why-need-for-third-party-cookies-in.html">the reader's login status and Blogger profile</a> can be determined by the blog display. In some cases, <a href="http://blogging.nitecruzr.net/2007/07/geolocation-where-are-my-readers.html">the readers location</a> is used. <br />
<br />
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. <br />
<br />
<b>The Tower Of Babel</b><br />
The <a href="http://blogging.nitecruzr.net/2007/09/blogger-dashboard-tower-of-babel.html">Tower Of Babel</a> is not going away, in this lifetime.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com1tag:blogger.com,1999:blog-24069595.post-84846453114916585412014-12-28T01:51:00.000-08:002018-09-25T12:49:56.838-07:00GeoLocation, And Our Use Of BloggerRecently, we've seen signs of confusion, from people who have problems with their Internet service, which shows them moving around their geographic region.<blockquote>I logged in to Blogger, with no problem, yesterday. Today, after logging in successfully, I am asked for more details, to prove my identity!!</blockquote>This blog owner has a problem with location based security. <br />
<br />
Not all Blogger blog owners or readers understand that <a href="http://blogging.nitecruzr.net/2014/01/country-code-alias-redirection-and.html">Country Local Domain Redirection</a>, and the ability to <a href="http://blogging.nitecruzr.net/2014/12/if-you-travel-be-prepared-to-prove.html">access one's Blogger / Google account</a> (and prevent others from accessing it), both depend upon the ability to determine the geographical location of each blog reader. <br />
<a name='more'></a><br />
Various Google features, like Country Local Domain Redirection, and Google login, use <a href="http://en.wikipedia.org/wiki/Geolocation" target="_blank">geolocation</a>, to identify the location of each reader. <br />
<br />
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) <a href="http://blogging.nitecruzr.net/2007/07/geolocation-where-are-my-readers.html">may each be in a different location</a>. <br />
<br />
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. <br />
<br />
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. <br />
<br />
This can be an unfortunate problem, with Country Local Domain redirection, with language detection, with login authentication, and / or the Location option in Post Editor. <br />
<br />
People located in one country, reading <a href="http://blogging.nitecruzr.net/2009/10/you-have-to-read-local-language.html">an unfamiliar language</a>, 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 <a href="http://blogging.nitecruzr.net/2014/12/if-you-travel-be-prepared-to-prove.html">prove their identity</a> - after successfully entering account name and password. <br />
<br />
Thanks to <a href="http://blogging.nitecruzr.net/2012/02/country-code-based-aliases-will.html">domain based filtering</a>, this may become a security issue for some blog owners, near country borders, who may not be able to maintain / publish their blogs. <br />
<br />
Unfortunately, geolocation, using the Internet Address (aka "IP" address), <a href="http://blogging.nitecruzr.net/2016/05/diagnosing-geographical-location-ip.html">will never return consistent and precise results</a>. Any location based processes will always provide fuzzy results, thanks to Internet services which load balance their network connections - and connect their customers through regionally located Internet gateways.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-5539227264528832992014-01-14T08:43:00.000-08:002016-09-06T15:58:36.570-07:00Country Code Alias Redirection, And GeoLocationOccasionally, we see signs of confusion, from people who understand <a href="http://blogging.nitecruzr.net/2012/06/confusion-over-reason-for-and-effect-of.html">Country Code Alias Redirection</a>, in general.<blockquote><div style="background-color: white;">I live in Hungary - but I am reading blogs with the ".sk" suffix!</div></blockquote>This blog reader knows about alias redirection - but does not understand why he is seeing redirection for Slovakia (".sk"), instead of Hungary (".hu"). <br />
<br />
Not all Blogger blog owners or readers understand that Country Code Alias Redirection depends upon the ability to determine the geographical location of each blog reader. <br />
<a name='more'></a><br />
Country Code Alias Redirection uses <a href="http://blogging.nitecruzr.net/2014/12/geolocation-and-our-use-of-blogger.html">geolocation</a>, to identify the location of each reader. <br />
<br />
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. <br />
<br />
This can be an unfortunate problem, with country code alias redirection, and with language detection. People located in one country, or <a href="http://blogging.nitecruzr.net/2009/10/you-have-to-read-local-language.html">reading a different language</a>, may not appreciate the confusion which follows. <br />
<br />
Thanks to <a href="http://blogging.nitecruzr.net/2012/02/country-code-based-aliases-will.html">domain based filtering</a>, this may cause a security issue for some blog owners, near country borders, who may not be able to maintain / publish their blogs. <br />
<br />
Unfortunately, geolocation, using the Internet Address (aka "IP" address), will never return precise results. Some readers will always show up, in the various visitor logs, under a different location than geography would have them.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-56684541033732850862013-04-14T12:12:00.001-07:002013-04-14T12:16:00.369-07:00The Tower Of Babble Comes Down Slowly - One Brick At A TimeI installed the Google auto translator - using a custom front end, which I helped develop - on this blog, <a href="http://blogging.nitecruzr.net/2008/02/make-your-blog-speak-more-languages.html">5 years ago</a>.
<br /><br />
I installed it originally because of the <a href="http://blogging.nitecruzr.net/2008/02/phishing-attack-warning-messages-from.html">February 2008 Kaspersky problem</a> with Blogger blogs - and hastily, because of the magnitude of the problem. I knew, at the time, that the Google auto translator was not 100% accurate.
<br /><br />
No auto translator will ever be 100% accurate. Every language in the world is always developing, as society and technology develops. There will always be nuances in every language, which are not yet detected by any one person - or by any one computer.
<br /><br />
That said, I think that it's obvious to many people, that auto translation is a legitimate feature on the Internet.
<br /><a name='more'></a><br />
If you've read this far, and you're using the translator to read this in a non English language, my thanks to you.
<br /><br />
I think that the Internet in general, and Blogger blogs - and translated Blogger blogs in particular, are going to do a lot to bring the various cultures and nations of the world closer together. Being a native of the USA, I speak only English with any degree of fluency. I have, at one time, attempted both French and Spanish, as secondary languages - but this is neither the time nor place for me to discuss my experiences in France and in Panama.
<br /><br />
I would never attempt to publish this blog, manually, in either French or Spanish - and certainly not any of the other 300+ languages which are present in the world. Since this blog has some value to Blogger blog owners and readers in general - and hopefully to some non English Blogger blog owners and readers - I think that using this blog, translated into other languages, has some value also.
<br /><br />
If you are reading this blog in a non English language - or if you know of specific phrases or words which are not translated, successfully, by the Google translator - you are invited to suggest any appropriate improvement to Google. Translate the phrase or word in question, using the <a href="http://translate.google.com" target="_blank">Google Translate</a> web page - and select "Rate translation" in the lower right corner of the translation result window.
<br /><br />If you publish a blog in a non English language, and you don't have an auto translator gadget on your blog, I hope that you will soon add such a feature. I'll even invite you to look at <a href="http://blogging.nitecruzr.net/2010/08/announcing-cumulus-in-your-language.html">Cumulus In Your Language</a>, and see if the offered non English selections are useful to you.<br /><br />
Just don't dismiss auto translation, because it's not currently 100% accurate. Use it - or don't use it - on any web page where it's useful, right now. But don't dismiss it, with prejudice.
<br /><br />
<a href="#Top">>> Top</a>Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-48550612125055319292012-07-21T14:59:00.001-07:002016-09-06T15:58:36.486-07:00Blogs, Written In Non Roman Character Languages, Have Trouble With Publishing Static PagesWe're seeing a few reports in <a href="http://groups.google.com/a/googleproductforums.com/forum/?hl=en&fromgroups#!categories/blogger/something-is-broken" target="_blank">Blogger Help Forum: Something Is Broken</a>, from owners of blogs which publish in languages that don't use Roman characters, about problems publishing static pages in their blogs. Supposedly, with the affected blogs containing multiple static pages, the pages are all being published with the same URL.<br />
<a name='more'></a><br />
The problem is thought to involve blogs published using the New Blogger GUI. Hopefully, by <a href="http://blogging.nitecruzr.net/2012/05/new-blogger-gui-is-still-not-ready-for.html">switching back to the Classic Blogger GUI</a>, the problem can be worked around, until Blogger Engineering can diagnose and fix the problem.<br />
<br />
We have <a href="http://productforums.google.com/d/topic/blogger/9VnQqv8YhQg/discussion" target="_blank">a Rollup Discussion</a> in <a href="http://groups.google.com/a/googleproductforums.com/forum/?hl=en&fromgroups#!categories/blogger/something-is-broken" target="_blank">Blogger Help Forum: Something Is Broken</a>, where we are asking for details, from owners of blogs affected.<ol><li>What is the URL of your blog?</li>
<li>In what language is the blog published?</li>
<li>Are you using the New Blogger GUI?</li>
<li>If you switch back to the Classic GUI, does that resolve your problem?</li>
<li>In what city / province / country do you live?</li>
</ol>Please answer as best you are able, to improve chances of Blogger Engineering finding and fixing the problem, as promptly as possible.<br />
<br />
<a href="#Top">>> Top</a>Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-86601880706073084612012-06-30T06:45:00.001-07:002015-06-23T16:57:45.991-07:00The World Wide Blogger Culture, And Date FormattingSince Blogger gave us The New Blogger GUI, in 2012, <a href="http://blogging.nitecruzr.net/2012/05/new-blogger-gui-is-still-not-ready-for.html">complaints about the New GUI</a> have been numerous, and impassioned.
<br /><br />
One complaint, seen occasionally, mentions the date / time setting wizard, in the Post Editor "Post settings" Schedule.<blockquote>In the new blogger interface, it is very hard to backdate content. You have to use the calendar GUI, you can't just type a date it. I have content going back 13 years, do you know how hard it is to click the left-arrow on the calendar 144 times to get to the proper date??? It's a nightmare!</blockquote>This is one person who needs a more flexible date setting wizard, in The New GUI.<br />
<br />
In criticising the new date setting wizard, we need to understand the reasons for the design. I don't think that Blogger designed the new wizard, and removed the ability to just type the date, simply because they wanted the new wizard to look shiny.<br />
<a name='more'></a><br />
Since Blogger gave us the ability to compose posts now, and have them published some time in the future, there have been problems with <a href="http://blogging.nitecruzr.net/2015/05/scheduled-posts-challenge-continues.html">scheduled posts not publishing properly</a>.
<br /><br />
Both posts published too early, and posts never published, have been the source of <a href="http://blogging.nitecruzr.net/2010/05/problems-observed-when-publishing-posts.html">many complaints</a>. The reason for many of these complaints were not obvious, however.<br />
<br />
When Blogger offered us <a href="http://blogging.nitecruzr.net/2008/05/future-scheduled-posts-now-thing-of.html">the scheduled posts option</a> in 2008, they made the ability to schedule posts quite simple. Unfortunately, they did not observe that <a href="http://blogging.nitecruzr.net/2011/01/world-wide-blogger-culture-and-date.html">the entire world does not type the date</a> in the same way. Many scheduling problems were caused by people who did not enter the date properly.<br />
<br />
Now that more people are using The New Blogger GUI, and the new date setting wizard, we are seeing significantly less complaints about posts not publishing at the right time (or at all). A large part of the reduction of such complaints, I believe, is due to the design of the new date setting wizard, which does not allow typing of the date - but forces you to explicitly select the month and year by sequential selection - and eliminates the ambiguity.<br />
<br />
Unfortunately, this ignores the needs of people who wish to back date (or forward date) by large time spans. So, Blogger <a href="http://blogging.nitecruzr.net/2015/05/scheduled-posts-challenge-continues.html">made the date setting wizard just a bit more flexible</a>.<br />
<br />
The latter tweak brought us another oddity - people who create a scheduled post, and set the date / time properly - but <a href="http://blogging.nitecruzr.net/2015/06/press-publish-to-schedule-post-to.html">never think to hit "Publish"</a>.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com3tag:blogger.com,1999:blog-24069595.post-6076432331413411952011-07-20T15:05:00.001-07:002014-10-04T12:40:38.596-07:00Transliteration Option Restored To AvailabilityAfter <a href="http://blogging.nitecruzr.net/2011/07/tranliteration-feature-is-disabled.html">several anxious weeks</a> of uncertainty, many people who publish blogs that use non Roman characters are happy to see that the Transliteration feature has been restored to availability. From the Classic Blogger GUI, Settings - Basic - Global Settings, we see a full array of supported languages. Alternatively, from the New Blogger GUI, the menu is at Settings - "Language and formatting".<br />
<a name='more'></a><br />
<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgOy70zqW6HPdtJ2wzYXq4MzIhO5exyhAT5x8jF-geFNaHqkZDtxa7hhZLE96U55oPyTlgtNfGhJZMYUM0-srbiJH6ZXSXRJksTMrAXJRXdIj829PYka1QrJW7KrqaIXRAVKf_tog/s1600/Transliteration+Menu+1.JPG" imageanchor="1" style="clear:left; float:left;margin-right:1em; margin-bottom:1em" target="_blank"><img border="0" height="232" width="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgOy70zqW6HPdtJ2wzYXq4MzIhO5exyhAT5x8jF-geFNaHqkZDtxa7hhZLE96U55oPyTlgtNfGhJZMYUM0-srbiJH6ZXSXRJksTMrAXJRXdIj829PYka1QrJW7KrqaIXRAVKf_tog/s320/Transliteration+Menu+1.JPG" /></a>Choices are now:<br />
Amharic, Arabic, Bengali, Greek, Persian, Gujarati, Hindi, Kannada, Malayalam, Marathi, Nepali, Punjabi, Russian, Sanskrit, Serbian, Tamil, Telugu, Tigrinya, Urdu<br />
<br clear=left /><br />
<br />
<a href="#Top">>> Top</a>Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-31375982249065154622011-07-15T17:28:00.000-07:002014-10-04T12:40:38.393-07:00The Tranliteration Feature Is DisabledOwners of Asian language blogs have been recently asking, in <a href="http://www.google.com/support/forum/p/blogger/label?lid=0271191b4249689a&hl=en">Blogger Help Forum: Something Is Broken</a><br />
<blockquote>Why can't I publish in Hindi (Kannada, Malayalam, Tamil, Telugu, ...) any more?</blockquote><br />
<hr />(Update 2011/07/20): The Transliteration feature has been <a href="http://blogging.nitecruzr.net/2011/07/transliteration-option-restored-to.html">returned to availability</a>.<br />
<hr /><br />
<a name='more'></a><br />
<br />
Blogger Known Issues <a href="http://knownissues.blogspot.com/2011/07/weve-temporarily-disabled.html" target="_blank">for Thursday, July 07, 2011</a> bears the bad news to us.<br />
<blockquote>We've temporarily disabled the transliteration feature until we sort out a few issues with the feature. Engineers are looking into this and hope to have the feature re-enabled shortly.</blockquote>If your blog requires any of these Asian character sets, you're going to have to be patient.<br />
<br />
There's no alternate solution, or quick fix, here - though a possible workaround is suggested by <i>Roberto: <a href="http://www.blogging.robertosblogs.net/2011/07/transliteration-post-editor.html" target="_blank">Transliteration - Post Editor Alternatives</a></i>.<br />
<br />
<a href="#Top">>> Top</a>Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com1tag:blogger.com,1999:blog-24069595.post-37179663485002058042011-05-26T10:42:00.000-07:002014-10-04T12:40:38.445-07:00Blog Owners Unable To Login To Blogger, Using "www.blogspot.com"This week, many unhappy blog owners report inability to login to Blogger, and access their dashboards. In some cases, they are seeing the well known "404 Not Found" error. For a few folks, this error comes from an odd habit - which used to be supported by Blogger - but no more.<br />
<a name='more'></a><br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhi1jBD_xhwCTg9c_7R-0_ILSVYmlNjFCAm3olNcT5_91IrYjhzTzFNdN4FgysvbKlaZ_l1HCn4To4W8XVNBt-6zX9x77Cx-n3rYhJlRqK4V6CGxd56JJDpS56vcCO5uhQe60tkRA/s1600/www.blogspot.com" imageanchor="1" style="clear:left; float:left;margin-right:1em; margin-bottom:1em" target="_blank"><img border="0" height="238" width="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhi1jBD_xhwCTg9c_7R-0_ILSVYmlNjFCAm3olNcT5_91IrYjhzTzFNdN4FgysvbKlaZ_l1HCn4To4W8XVNBt-6zX9x77Cx-n3rYhJlRqK4V6CGxd56JJDpS56vcCO5uhQe60tkRA/s320/www.blogspot.com" /></a><br />
"<a href="http://www.blogspot.com" target="_blank">www.blogspot.com</a>", which used to redirect to "<a href="http://www.blogger.com" target="_blank">www.blogger.com</a>", now does not.<br />
<br />
If you use "www.blogspot.com" to access Blogger, access your dashboard, or to login, this is why you cannot access Blogger, access your dashboard, or login.<br />
<br clear=left /><br />
<br />
Update your bookmarks, and change your habits, when you login to Blogger. Don't use "www.blogspot.com" <a href="http://blogging.nitecruzr.net/2010/10/logging-in-to-blogger-with-your-google.html">to access Blogger</a> - use "www.blogger.com". If you need to <a href="http://blogging.nitecruzr.net/2010/11/you-may-not-have-to-speak-local.html">avoid the local language redirect</a>, use "www.blogger.com/start?hl=en" (for English access to Blogger), or use "www.blogger.com/start?hl=xx" (for any supported alternative <a href="http://en.wikipedia.org/wiki/ISO_639-1" target="_blank">language code</a> "xx").<br />
<br />
<a href="#Top">>> Top</a>Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com15tag:blogger.com,1999:blog-24069595.post-6318285051678129542011-01-16T10:51:00.002-08:002015-05-30T18:26:25.905-07:00The World Wide Blogger Culture, And Date FormattingThe 21st Century is the beginning of new experiences for mankind.
<br /><br />
The Internet in general, and Blogger blogging in particular, are providing opportunities unparalleled in history - people of all nations and locations are coming together, casually and freely, to get acquainted. And with the opportunities come many challenges - some major, and others seemingly minor.<br />
<br />
One seemingly minor issue, with a significance which may not be realised by everybody, is how we write the date. In the USA, we generally write it as "mm/dd/yy", which stands, in computer speak, for "Month / Day / Year". A variation here is "mm/dd/yyyy", which denotes the year entered, and includes the century - which is also an important detail.<br /><a name='more'></a>
<br />
Such <a href="http://blogging.nitecruzr.net/2015/05/scheduled-posts-challenge-continues.html">an insignificant detail</a> - date and time format? You might think so - and you would be wrong.
<br /><br />
Some Europeans use the "dd/mm/yyyy" format, and would write today's date as "16/01/2011" or "16 January 2011". Most blog owners in the USA would write "01/16/2011", or "January 16, 2011". As a techie, I am in the habit of writing "2011/01/16".<br />
<br />
The Blogger Settings - Formatting - "Archive Index Date Format" and "Timestamp Format" setting together offer hints of the opportunities - and challenges - provided by Blogger. Look at the wide range of choices offered.<br />
<ul><li>Date Header Format<ol><li>Jan 16, 2011</li>
<li>January 16, 2011</li>
<li>Sunday, January 16, 2011</li>
<li>1/16/11</li>
<li>Sunday, January 16, 2011</li>
<li>1/16/2011</li>
<li>1.16.2011</li>
<li>20110116</li>
<li>2011/01/16</li>
<li>2011-01-16</li>
<li>16.1.11</li>
<li>Sunday</li>
<li>Sunday, January 16</li>
<li>January 16, 2011</li>
<li>16 January 2011</li>
<li>16 January, 2011</li>
</ol></li>
<li>Archive Index Date Format<ol><li>1/1/11 - 2/1/11</li>
<li>01/01/2011 - 02/01/2011</li>
<li>01/2011 - 02/2011</li>
<li>2011/01 - 2011/02</li>
<li>1/1/11</li>
<li>01/2011</li>
<li>01.2011</li>
<li>201101</li>
<li>01.11</li>
<li>2011-01</li>
<li>2011.01</li>
<li>January 2011</li>
<li>2011/01</li>
<li>01/11</li>
<li>11_01</li>
<li>01_11</li>
</ol></li>
</ul><br />
Having provided the background details, I will give you an example of the ambiguity problem. If I enter "12/1/11" is that to be interpreted as<ol><li>January 12, 2011.</li>
<li>December 1, 2011.</li>
<li>January 11, 2012.</li>
</ol><br />
The need to state the century is significant too. "12/1/30" is similarly ambiguous.<ol><li>January 30, 1912.</li>
<li>January 12, 1930.</li>
<li>December 1, 1930.</li>
<li>January 30, 2012.</li>
<li>January 12, 2030.</li>
<li>December 1, 2030.</li>
</ol><br />
One place where this ambiguity is relevant is when <a href="http://blogging.nitecruzr.net/2010/05/problems-observed-when-publishing-posts.html">entering the date for "Scheduled Posts"</a>. Complaints of posts that were published immediately (though scheduled for later publication), and posts that did not publish (and were found with a status of "Scheduled", in "<a href="http://blogging.nitecruzr.net/2008/04/edit-posts-menu.html">Edit Posts</a>"), are occasionally seen in <a href="http://www.google.com/support/forum/p/blogger/label?lid=0271191b4249689a&hl=en">Blogger Help Forum: Something Is Broken</a>.<br />
<br />
If you look in "Post Options", which is left and below the post content window in Post Editor, you'll find the "Post date and time" dialogue. The default selection there will vary<ul><li>"Automatic" (for new posts).</li>
<li>The date and time when the post was published (for posts already published).</li>
<li>A future date and time (for a post scheduled to be published).</li>
</ul>The first box beneath "Set date and time" contains the relevant date (published, or scheduled). Besides observing the current content of the date box, there is nothing to indicate the appropriate date format, that is expected by the dialogue.<br />
<br />
It does not take a lot of imagination to see what would happen, if a European blog owner was to enter "7/1/11" (meaning 7 January, 2011), and wind up with a post scheduled for publication July 1, 2011.<br />
<br />
<hr />(Update 2012/06/30): Blogger has redesigned the date setting wizard under The New Blogger GUI, and eliminated the ambiguity - but <a href="http://blogging.nitecruzr.net/2012/06/world-wide-blogger-culture-and-date.html">not without some criticism</a>.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com2tag:blogger.com,1999:blog-24069595.post-88534338570242973792010-11-21T13:35:00.000-08:002015-03-13T20:48:33.780-07:00You May Not Have To Speak The Local LanguageBlogger and Google want to make their services available to the entire world - and this involves recognising that <a href="http://blogging.nitecruzr.net/2007/06/you-have-to-speak-language.html">the entire world does not speak English</a>.
<br /><br />
Not only is the English language not spoken by the majority of the worlds inhabitants, it's not even the second most common. With this detail in mind, Blogger / Google tries to display their pages in the language of the local inhabitants, based on geo location of the Internet connection.<br /><a name='more'></a>
<br />
If you are in a land not your own, and you don't speak the local language, you may not do well reading the language either.
<br /><br />
When you want to use Blogger or Google, you may need to see the initial display in English (or in whatever non local language you speak). Fortunately, Blogger and Google have provided for this situation.<ul><li>With Blogger, "<a href="https://www.blogger.com"target="_blank">https://www.blogger.com</a>" gives you a Blogger sign in page in the local language.<ul><li>If you need to see the sign in page in English, you can use "<a href="https://www.blogger.com/start?hl=en" target="_blank">https://www.blogger.com/start?hl=en</a>". The Draft equivalent, "<a href="https://draft.blogger.com/start?hl=en" target="_blank">https://draft.blogger.com/start?hl=en</a>", may or may not work, similarly, to let us use the New GUI (2011) Blogger.</li>
<li>If you need the page in your own language, use "https://www.blogger.com/start?hl=xx", where "xx" is the code for your language.</li>
<li>To "permanently" set the language that you want to use, from this computer, use the Blogger <a href="https://www.blogger.com/language.g" target="_blank">Language Selection</a> wizard.</li>
</ul></li>
<li>With Google, "<a href="https://www.google.com"target="_blank">https://www.google.com</a>" gives you the page in the local language. If you need to see the page in English, you can use "<a href="https://google.com/ncr" target="_blank">https://google.com/ncr</a>".</li>
</ul><br />
And if you can login to Blogger, you can use <a href="http://blogging.nitecruzr.net/2007/09/tower-of-babble-becomes-slightly-lower.html">the Language Selector list</a>, where you will find your language selection, in your own language, somewhere in the list. You can set your dashboard language, from the list.Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com3tag:blogger.com,1999:blog-24069595.post-62175027865224970662010-08-08T09:26:00.000-07:002010-08-08T09:31:20.183-07:00Cumulus "In Your Language" Multi Lingual Translation Expands To 11 LanguagesLast week, <a href="http://www.nitecruzr.net/" target="_blank">Nitecruzr Dot Net</a> and <a href="http://www.robertosblogs.net/" target="_blank">RobertosBlogs Dot Net</a> together announced the new Cumulus "In Your Language" non English translator gadget, which support blogs published in any of 7 different non English languages. Now, we have added 4 more languages - Arabic, Chinese (Simplified), Japanese, and Portuguese - to the supported population.<br />
<br />
If your blog is published in any of these languages, you can now provide dynamic translation of your blog or website, by your readers, into any of the other languages, using the Google Translator engine.<ul><li><a href="http://cumulus-ar.nitecruzr.net/2010/08/cumulus-your-language-code.html" target="_blank">Arabic</a></li>
<li><a href="http://cumulus-zh-cn.nitecruzr.net/2010/08/cumulus-your-language-code.html" target="_blank">Chinese</a> (Simplified)</li>
<li><a href="http://cumulus-zh-tw.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Chinese</a> (Traditional)</li>
<li><a href="http://cumulus-fr.nitecruzr.net/2009/10/cumulus-your-language-code.html" target="_blank">French</a></li>
<li><a href="http://cumulus-hi.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Hindi</a></li>
<li><a href="http://cumulus-id.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Indonesian</a></li>
<li><a href="http://cumulus-it.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Italian</a></li>
<li><a href="http://cumulus-ja.nitecruzr.net/2010/08/cumulus-your-language-code.html" target="_blank">Japanese</a></li>
<li><a href="http://cumulus-pt.nitecruzr.net/2010/08/cumulus-your-language-code.html" target="_blank">Portuguese</a></li>
<li><a href="http://cumulus-ru.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Russian</a></li>
<li><a href="http://cumulus-es.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Spanish</a></li>
</ul><br />
We hope to add additional languages, as need and resources become available. And, we'll add to the target languages, for all source languages, as Google expands the base of their translation engine.<br />
<br />
<a href="#Top">>> Top</a>Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com1tag:blogger.com,1999:blog-24069595.post-49929330008113746482010-08-03T09:01:00.000-07:002010-08-08T09:30:54.222-07:00Announcing Cumulus "In Your Language" Multi Lingual TranslationJust a bit more than 2 years ago, NiteCruzr Dot Net became a part of the world wide culture, by providing <a href="http://blogging.nitecruzr.net/2008/02/make-your-blog-speak-more-languages.html">an easy to install translation bar</a>, for blogs published in English. That's a start, anyway.<br />
<br />
What "we" (the "English" speaking population of blog owners) don't always realise is that neither the entire world population, nor the entire web population, speaks English. The English language isn't the most commonly spoken language in the world - nor is it <a href="http://en.wikipedia.org/wiki/File:Native_speakers_in_the_World.jpg" target="_blank">even number two</a>. Blogger blogs are being published in many non English languages, and bloggers need to support that reality.<br />
<br />
Now, Nitecruzr Dot Net, in partnership with <a href="http://www.blogging.robertosblogs.net/2010/08/foreign-language-translators.html" target="_blank">Robertosblogs Dot Net</a>, announces the next step in multi-lingual blogging. <a href="http://cumulus-en.nitecruzr.net/" target="_blank">Cumulus In Your Language</a> now provides multi-lingual translation from any of 7 non English languages, to any of the other provided languages.<ul><li><a href="http://cumulus-zh-tw.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Chinese</a> (Traditional)</li>
<li><a href="http://cumulus-fr.nitecruzr.net/2009/10/cumulus-your-language-code.html" target="_blank">French</a></li>
<li><a href="http://cumulus-hi.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Hindi</a></li>
<li><a href="http://cumulus-id.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Indonesian</a></li>
<li><a href="http://cumulus-it.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Italian</a></li>
<li><a href="http://cumulus-ru.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Russian</a></li>
<li><a href="http://cumulus-es.nitecruzr.net/2010/08/cumulus-in-your-language-code.html" target="_blank">Spanish</a></li>
</ul><br />
If your blog is published in any of the above languages, check out the Your Language translator gadget installation procedure in <a href="http://cumulus-en.nitecruzr.net/" target="_blank">Cumulus - EN</a>. Other languages will be added, as demand and resources exist.<br />
<br />
<a href="#Top">>> Top</a>Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com0tag:blogger.com,1999:blog-24069595.post-64755354536693579912010-05-06T08:59:00.000-07:002015-03-03T10:43:48.202-08:00Problems Observed When Publishing Posts With Changed DatesRecently, we've seen reports, in <a href="http://www.google.com/support/forum/p/blogger/label?lid=0271191b4249689a&hl=en">Blogger Help Forum: Something Is Broken</a> about some oddities observed when publishing <a href="http://blogging.nitecruzr.net/2006/11/changing-post-date.html">posts with changed dates</a>.<blockquote>I back dated a post, but it won't publish.</blockquote>or<blockquote>I published a post with a scheduled date, and it has already published.</blockquote><br />
What's going on here? If you're observing this problem, please try and help us diagnose its spread.<ul><li>What date / time format is the blog set to?</li>
<li>What time zone is the blog set to?</li>
<li>What date / time format is the computer, where you setup the blog, set to?</li>
<li>What date / time format is the computer, where you published the post, set to?</li>
<li>What time zone is the computer, where you setup the blog, set to?</li>
<li>What time zone is the computer, where you published the post, set to?</li>
<li>What language is the blog published in?</li>
<li>What language is the computer, from where you published the scheduled post, set to?</li>
<li>Are the two computers - used for setting up the blog, and used for publishing the post, the same?</li>
<li>What browser did you use, when setting up the blog, and when publishing the posts?</li>
</ul>Be as generous, and as precise as possible, and help us to see if there is <a href="http://blogging.nitecruzr.net/2011/01/world-wide-blogger-culture-and-date.html">an affinity to this problem</a>. And <a href="http://blogging.nitecruzr.net/feeds/6475535453669357991/comments/default">subscribe to the comments feed</a> for this post, to keep up with ongoing developments.<br />
<br />
<a href="#Top">>> Top</a>Nitecruzrhttp://www.blogger.com/profile/08069634565746003311noreply@blogger.com2