Wednesday, October 13, 2010

SEO Tips for Drupal

Many of Content Management System (CMS) software generate the dynamic page when user made a request. This dynamic page usually has question mark ("?") at the end of its file name. Drupal also has this characteristic, for the example http://drupalsitesample.com/?q=node/3. For a better Search Engine Optimization (SEO), it will be worthwhile to read the statement from Google's webmaster guidelines which stated that the static page is crawled better by the search engine than the dynamic page.

If you decide to use dynamic pages (i.e., the URL contains a "?" character), be aware that not every search engine spider crawls dynamic pages as well as static pages. It helps to keep the parameters short and the number of them few. 

Clean URLs

Drupal has a feature called Clean URLs. That feature will eliminate the ?q= in the URL. So, without ?q= the URL will become http://drupalsitesample.com/node/3. That URL is more like a static page URL which is said can be crawled better by the search engine. Before you can use this feature, make sure your Apache mod_rewrite module is enabled. To enable to Clean URLs feature, you can open menu Administer - Site configurations - Clean URLs. After that, you have to choose the Enabled option then click Save configuration. Drupal Clean URLs
 
URL Aliases

We can also rename Drupal URLs by enabling the Path module. This module is already bundled with Drupal. By using URL Aliases feature, we can rename the URL like http://drupalsitesample.com/node/3 to a more readable URL like http://drupalsitesample.com/drupal-seo-tips. This kind of URL will be searchable via Google with inurl: prefix. To enable the Path module, you can open menu Administer - Site building - Modules and give checkmark on Pathauto checkbox. After that, click the Save configuration button. Enabling Path Module After the Path module is enabled, you can rename the URL of your content by filling the URL path settings field when you creating or editting content. Rename URL
Pathauto Module
 
Renaming URL manually can be a tiring job. But, there is a module that can help you to automatically generate URL aliases. That module name is Pathauto and can be downloaded from http://drupal.org/project/pathauto. Before downloading Pathauto, remember to download Token module from http://drupal.org/project/token because Pathauto requires Token.
To enable to Pathauto module, you can open menu Administer - Site building - Modules. Give check on Token and Pathauto modules. After that, click the Save configuration button.
After the Pathauto module is enabled, it will automatically generate the URL alias for your content when you creating new content. For your older content which haven't aliased before, you can edit them and give a check on Automatic alias checkbox on the URL path settings form.

Automatic alias

The default pattern for the generated URL alias is content/[title-raw]. The [title-raw] will be generated from your content title. So, if your content title is Welcome to my website, Pathauto will generate the URL alias such as content/welcome-to-my-website. You can change this pattern with this following steps.

  1. Click menu Administer - Site building - URL aliases then click Automated alias settings tab.
  2. Click Node path settings. You can change the pattern by modifying the content in this field.

    Automated alias settings
  3. To see the complete Replacement patterns, you can click on Replacement patterns.
  4. For the example, I modify the Default path pattern into content/[yyyy]/[mm]/[dd]/[title-raw].
  5. Click Save configuration when you ready.
  6. So, if I create a content titled My New Content on 1-February-2010, the aliased URL will be content/2010/02/01/my-new-content.


 

sitemap.html

http://drupalconcepts.blogspot.com
http://drupalconcepts.blogspot.com/
http://drupalconcepts.blogspot.com/2010/10/whats-new-in-drupal-7.html
http://drupalconcepts.blogspot.com/2010/10/google-site-verification.html
http://drupalconcepts.blogspot.com/2010/10/multilingual-taxonomy.html
http://drupalconcepts.blogspot.com/2010/10/drupal-7-performance-improvements.html
http://drupalconcepts.blogspot.com/2010/10/displaying-popular-content-in-drupal.html
http://drupalconcepts.blogspot.com/2010/10/seo-tips-in-drupal.html
http://drupalconcepts.blogspot.com/2010/10/printer-module-and-wkhtmltopdf-tool-for.html
http://drupalconcepts.blogspot.com/2010/10/use-of-i18n-module-to-creae.html
http://drupalconcepts.blogspot.com/2010_10_01_archive.html
http://drupalconcepts.blogspot.com/search?updated-min=2010-01-01T00%3A00%3A00-08%3A00&updated-max=2011-01-01T00%3A00%3A00-08%3A00&max-results=9
http://drupalconcepts.blogspot.com/feeds/posts/default
http://drupalconcepts.blogspot.com/2010/10/drupalconceptsblogspotcom-page-rank.html
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-06T00%3A36%3A00-07%3A00&max-results=2
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-09T11%3A22%3A00-07%3A00&max-results=2&reverse-paginate=true
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-13T03%3A05%3A00-07%3A00&max-results=2
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-09T11%3A22%3A00-07%3A00&max-results=2
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-13T03%3A05%3A00-07%3A00&max-results=2&reverse-paginate=true
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-08T06%3A17%3A00-07%3A00&max-results=2
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-08T06%3A17%3A00-07%3A00&max-results=2&reverse-paginate=true
http://drupalconcepts.blogspot.com/feeds/565808327907273514/comments/default
http://drupalconcepts.blogspot.com/feeds/405522799784493656/comments/default
http://drupalconcepts.blogspot.com/feeds/211474663707931413/comments/default
http://drupalconcepts.blogspot.com/feeds/4986998599612954889/comments/default
http://drupalconcepts.blogspot.com/feeds/8884785844001694069/comments/default
http://drupalconcepts.blogspot.com/feeds/7703900582403463564/comments/default
http://drupalconcepts.blogspot.com/feeds/1871752320084566144/comments/default
http://drupalconcepts.blogspot.com/feeds/7603089723564142202/comments/default
http://drupalconcepts.blogspot.com/feeds/1574826607156278712/comments/default

urllist.txt

http://drupalconcepts.blogspot.com
http://drupalconcepts.blogspot.com/
http://drupalconcepts.blogspot.com/2010/10/whats-new-in-drupal-7.html
http://drupalconcepts.blogspot.com/2010/10/google-site-verification.html
http://drupalconcepts.blogspot.com/2010/10/multilingual-taxonomy.html
http://drupalconcepts.blogspot.com/2010/10/drupal-7-performance-improvements.html
http://drupalconcepts.blogspot.com/2010/10/displaying-popular-content-in-drupal.html
http://drupalconcepts.blogspot.com/2010/10/seo-tips-in-drupal.html
http://drupalconcepts.blogspot.com/2010/10/printer-module-and-wkhtmltopdf-tool-for.html
http://drupalconcepts.blogspot.com/2010/10/use-of-i18n-module-to-creae.html
http://drupalconcepts.blogspot.com/2010_10_01_archive.html
http://drupalconcepts.blogspot.com/search?updated-min=2010-01-01T00%3A00%3A00-08%3A00&updated-max=2011-01-01T00%3A00%3A00-08%3A00&max-results=9
http://drupalconcepts.blogspot.com/feeds/posts/default
http://drupalconcepts.blogspot.com/2010/10/drupalconceptsblogspotcom-page-rank.html
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-06T00%3A36%3A00-07%3A00&max-results=2
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-09T11%3A22%3A00-07%3A00&max-results=2&reverse-paginate=true
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-13T03%3A05%3A00-07%3A00&max-results=2
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-09T11%3A22%3A00-07%3A00&max-results=2
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-13T03%3A05%3A00-07%3A00&max-results=2&reverse-paginate=true
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-08T06%3A17%3A00-07%3A00&max-results=2
http://drupalconcepts.blogspot.com/search?updated-max=2010-10-08T06%3A17%3A00-07%3A00&max-results=2&reverse-paginate=true
http://drupalconcepts.blogspot.com/feeds/565808327907273514/comments/default
http://drupalconcepts.blogspot.com/feeds/405522799784493656/comments/default
http://drupalconcepts.blogspot.com/feeds/211474663707931413/comments/default
http://drupalconcepts.blogspot.com/feeds/4986998599612954889/comments/default
http://drupalconcepts.blogspot.com/feeds/8884785844001694069/comments/default
http://drupalconcepts.blogspot.com/feeds/7703900582403463564/comments/default
http://drupalconcepts.blogspot.com/feeds/1871752320084566144/comments/default
http://drupalconcepts.blogspot.com/feeds/7603089723564142202/comments/default
http://drupalconcepts.blogspot.com/feeds/1574826607156278712/comments/default

sitemap.xml






http://drupalconcepts.blogspot.com
1.00
daily


http://drupalconcepts.blogspot.com/
1.00
daily


http://drupalconcepts.blogspot.com/2010/10/whats-new-in-drupal-7.html
0.80
daily


http://drupalconcepts.blogspot.com/2010/10/google-site-verification.html
0.80
daily


http://drupalconcepts.blogspot.com/2010/10/multilingual-taxonomy.html
0.80
daily


http://drupalconcepts.blogspot.com/2010/10/drupal-7-performance-improvements.html
0.80
daily


http://drupalconcepts.blogspot.com/2010/10/displaying-popular-content-in-drupal.html
0.80
daily


http://drupalconcepts.blogspot.com/2010/10/seo-tips-in-drupal.html
0.80
daily


http://drupalconcepts.blogspot.com/2010/10/printer-module-and-wkhtmltopdf-tool-for.html
0.80
daily


http://drupalconcepts.blogspot.com/2010/10/use-of-i18n-module-to-creae.html
0.78
daily


http://drupalconcepts.blogspot.com/2010_10_01_archive.html
0.69
daily


http://drupalconcepts.blogspot.com/search?updated-min=2010-01-01T00%3A00%3A00-08%3A00&updated-max=2011-01-01T00%3A00%3A00-08%3A00&max-results=9
0.69
daily


http://drupalconcepts.blogspot.com/feeds/posts/default
0.61
daily


http://drupalconcepts.blogspot.com/2010/10/drupalconceptsblogspotcom-page-rank.html
0.56
daily


http://drupalconcepts.blogspot.com/search?updated-max=2010-10-06T00%3A36%3A00-07%3A00&max-results=2
0.53
daily


http://drupalconcepts.blogspot.com/search?updated-max=2010-10-09T11%3A22%3A00-07%3A00&max-results=2&reverse-paginate=true
0.53
daily


http://drupalconcepts.blogspot.com/search?updated-max=2010-10-13T03%3A05%3A00-07%3A00&max-results=2
0.53
daily


http://drupalconcepts.blogspot.com/search?updated-max=2010-10-09T11%3A22%3A00-07%3A00&max-results=2
0.53
daily


http://drupalconcepts.blogspot.com/search?updated-max=2010-10-13T03%3A05%3A00-07%3A00&max-results=2&reverse-paginate=true
0.53
daily


http://drupalconcepts.blogspot.com/search?updated-max=2010-10-08T06%3A17%3A00-07%3A00&max-results=2
0.53
daily


http://drupalconcepts.blogspot.com/search?updated-max=2010-10-08T06%3A17%3A00-07%3A00&max-results=2&reverse-paginate=true
0.52
daily


http://drupalconcepts.blogspot.com/feeds/565808327907273514/comments/default
0.52
daily


http://drupalconcepts.blogspot.com/feeds/405522799784493656/comments/default
0.52
daily


http://drupalconcepts.blogspot.com/feeds/211474663707931413/comments/default
0.52
daily


http://drupalconcepts.blogspot.com/feeds/4986998599612954889/comments/default
0.52
daily


http://drupalconcepts.blogspot.com/feeds/8884785844001694069/comments/default
0.52
daily


http://drupalconcepts.blogspot.com/feeds/7703900582403463564/comments/default
0.52
daily


http://drupalconcepts.blogspot.com/feeds/1871752320084566144/comments/default
0.52
daily


http://drupalconcepts.blogspot.com/feeds/7603089723564142202/comments/default
0.52
daily


http://drupalconcepts.blogspot.com/feeds/1574826607156278712/comments/default
0.52
daily

Page Rank Checker

Printer module and wkhtmltopdf tool for pdf version

If you want to generate the following printer-friendly versions of any node:
  • Printer-friendly version (webpage format) (at www.example.com/print/nid)
  • PDF version (at www.example.com/printpdf/nid)
  • Send by-email (at www.example.com/printmail/nid)
where nid is the node id of content to render,then follow these steps:

First of all download the "print" module from here http://drupal.org/project/print

Install and Enable the module.

Now for pdf version you need to install a third party tool called "wkhtmltopdf"

Download wkhtmltopdf from http://code.google.com/p/wkhtmltopdf/downloads/list. 
You can choose to download the source and compile it or simply download the static binary,which doesn't require you to complile anything.
 
Place the wkhtmltopdf executable into the path as "sites/all/modules/print/lib" 

Thats all,now go to admin->settings->print configure as you want :)

Tuesday, October 12, 2010

Drupal 7 - performance improvements

This post highlights some of the improvements developed for the upcoming Drupal 7 release.


Drupal 7 has made its caching system more easily plugablele - to allow for easier memcache integration, for example. It has also enabled caching HTTP headers to be set so that logged out users can cache entire pages locally as well as improve compatibility with reverse proxies and content distribution networks (CDNs). There is also a patch waiting which reduces both the response size and the time taken to generate 404 responses for inlined page assets. Depending on the type of 404 (CSS have a larger effect than images, for example) the slower 404s were adding 0.5 to 1 second to the calling page load times.


Drupal currently has the ability to aggregate multiple CSS and JavaScript files by concatenating them into a smaller number of files to reduce the number of HTTP requests. There is a patch in the queue for Drupal 7 that could allow aggregation to be enabled by default, which is great because the large number of individual files can add anything from 0-1.5 seconds to page loads.

One issue that has become apparent with the Drupal 6 aggregation system is that users can end up downloading aggregate files that include a large amount of duplicate code. On one page the aggregate may contain files a, b and c, whilst on a second page the aggregate may contain files a, b and d - the “c” and “d” files being added conditionally on specific pages. This breaks the benefits of browser caching and slows down subsequent page loads. Benchmarking on core alone shows that avoiding duplicate aggregates can save over a second across 5 page loads. A patch has already been committed that means files need to be explicitly added to the aggregate, and fix Drupal core to add appropriate files to the aggregate unconditionally.

Drupal has supported gzip compression of HTML output for a long time, however for CSS and JavaScript, the files are delivered directly by the webserver, so Drupal has less control. There are webserver based compressors such as Apache’s mod_deflate, but these are not always available. A patch is in the queue that stores compressed versions of aggregated files on write and uses rewrite and header directives in .htaccess that allow these files to be served correctly. Benchmarks show that this patch can make initial page views 20-60% faster, saving anything from 0.3 to 3 seconds total.

The Drupal 7 release promises some real improvements from a front-end performance point of view. Other performance optimizations will no doubt continue to appear and be refined in contributed modules and themes, as well as in site building best practices and documentation. In Drupal 8 we will hopefully see further improvements in the CSS/JS file aggregation system, increased high-level caching effectiveness and hopefully more tools to help site builders reduce file sizes. If you have yet to try Drupal, download it now and give it a try and tell us in the comments if your site performance improves! :)

Saturday, October 9, 2010

What's new in Drupal 7

Drupal 7 is in its final stages of development. Download the latest pre-release version if you would like to test it out now.

Here is a summary of changes introduced to Drupal 7. You can also see the complete Drupal change log.

 New Minimum System Requirements:

This is not a complete list of requirements. Please read the complete list of requirements.
  • Database: MySQL 5.0.15 or PostgreSQL 8.3
  • PHP Version 5.2 or higher
  • PHP Memory: 40M - 64M

Security:


  • More secure implementation for scheduled tasks (cron.php).
  • More secure password system.
  • More secure log-in system.
  • Modules can be updated via the web.

Usability:

  • Administrative links to edit existing page elements are now available on each web page, without having to go to an administration page first.
  • Improved support for integration of WYSIWYG editors.
  • Added more drag-and-drop for administrative tasks.
  • Permissions now have the ability to handle more meta-data (permissions now have a description).
  • User 1 created as part of the installation process.
  • Added features to the default install profile (tagging on the Article content type).
  • Setting up automated task runs (cron) can now be achieved via Drupal's configuration alone, without having to install any scripts on the web server.
  • Redesigned password strength validator to make it kinder and gentler, and clearer.
  • Renamed "input formats" to "text formats".
  • Added support for default text formats to be assigned on a per-role basis.
  • Moved text format permissions to the main permissions page
  • Added "vertical tabs", a reusable interface component that features automatic summaries and increases usability.
  • Improved time zone support
  • Removed per-user themes: Contributed modules with similar functionality are available.
  • Added new "Shortcuts" module to allow user to create their own menu for the pages they visit the most.

Database:

  • Added query builders for INSERT, UPDATE, DELETE, MERGE, and SELECT queries.
  • Support for master/slave replication, transactions, multi-insert queries,delayed inserts, and other features.
  • Added support for the SQLite database engine.
  • Default to InnoDB engine, rather than MyISAM, on MySQL when available for greater scalability and data integrity.

Several Performance Improvements Implemented

News aggregator:

  • Added OPML import functionality for RSS feeds.
  • Added feed update options.

Theme system:

  • Removed the Bluemarine, Chameleon and Pushbutton themes. These themes live on as contributed themes
  • Added "Bartik" theme as the default user interface theme.
  • Added "Seven" theme as the default administration interface theme.
  • Added "Stark" theme to make analyzing Drupal's default HTML and CSS easier.

File handling:

  • Files are now first class Drupal objects with file_load(), file_save(),
    and file_validate() functions and corresponding hooks.
  • Files use PHP stream wrappers to enable support for both public and private files and to support pluggable storage mechanisms and access to remote resources (e.g. S3 storage or Flickr photos).
  • Added a field specifically for uploading files, previously provided by
    the contributed module FileField.

Image handling:

  • Improved image handling, including better support for add-on image
    libraries.
  • Added a field specifically for uploading images, previously provided by the contributed module ImageField.

Better Support for Multisite Installations

Added ability to add custom fields

  • Provides most of the features of the former Content Construction Kit (CCK) module.
  • Custom data fields may be attached to nodes, users, comments and taxonomy terms.
  • Node bodies and teasers are now fields instead of being a hard-coded property of node objects.
  • Fields are translatable.

Installer can be run from the command line

JavaScript changes

  • Upgraded the core JavaScript library to jQuery version 1.4.2.
  • Upgraded the jQuery Forms library to 2.36.
  • Added jQuery UI 1.8, which allows improvements to Drupal's user experience.

 

 


 

 


 


 


 



 

 

 

 


 


 

google-site-verification: googled875852dfe83acf8.html

Friday, October 8, 2010

SEO Tips In Drupal

Many of Content Management System (CMS) software generate the dynamic page when user made a request. This dynamic page usually has question mark ("?") at the end of its file name. Drupal also has this characteristic, for the example http://drupalsitesample.com/?q=node/3. For a better Search Engine Optimization (SEO), it will be worthwhile to read the statement from Google's webmaster guidelines which stated that the static page is crawled better by the search engine than the dynamic page.

If you decide to use dynamic pages (i.e., the URL contains a "?" character), be aware that not every search engine spider crawls dynamic pages as well as static pages. It helps to keep the parameters short and the number of them few. 

Clean URLs

Drupal has a feature called Clean URLs. That feature will eliminate the ?q= in the URL. So, without ?q= the URL will become http://drupalsitesample.com/node/3. That URL is more like a static page URL which is said can be crawled better by the search engine. Before you can use this feature, make sure your Apache mod_rewrite module is enabled. To enable to Clean URLs feature, you can open menu Administer - Site configurations - Clean URLs. After that, you have to choose the Enabled option then click Save configuration. Drupal Clean URLs
 
URL Aliases

We can also rename Drupal URLs by enabling the Path module. This module is already bundled with Drupal. By using URL Aliases feature, we can rename the URL like http://drupalsitesample.com/node/3 to a more readable URL like http://drupalsitesample.com/drupal-seo-tips. This kind of URL will be searchable via Google with inurl: prefix. To enable the Path module, you can open menu Administer - Site building - Modules and give checkmark on Pathauto checkbox. After that, click the Save configuration button. Enabling Path Module After the Path module is enabled, you can rename the URL of your content by filling the URL path settings field when you creating or editting content. Rename URL
Pathauto Module
 
Renaming URL manually can be a tiring job. But, there is a module that can help you to automatically generate URL aliases. That module name is Pathauto and can be downloaded from http://drupal.org/project/pathauto. Before downloading Pathauto, remember to download Token module from http://drupal.org/project/token because Pathauto requires Token.
To enable to Pathauto module, you can open menu Administer - Site building - Modules. Give check on Token and Pathauto modules. After that, click the Save configuration button.
After the Pathauto module is enabled, it will automatically generate the URL alias for your content when you creating new content. For your older content which haven't aliased before, you can edit them and give a check on Automatic alias checkbox on the URL path settings form.

Automatic alias

The default pattern for the generated URL alias is content/[title-raw]. The [title-raw] will be generated from your content title. So, if your content title is Welcome to my website, Pathauto will generate the URL alias such as content/welcome-to-my-website. You can change this pattern with this following steps.

  1. Click menu Administer - Site building - URL aliases then click Automated alias settings tab.
  2. Click Node path settings. You can change the pattern by modifying the content in this field.

    Automated alias settings
  3. To see the complete Replacement patterns, you can click on Replacement patterns.
  4. For the example, I modify the Default path pattern into content/[yyyy]/[mm]/[dd]/[title-raw].
  5. Click Save configuration when you ready.
  6. So, if I create a content titled My New Content on 1-February-2010, the aliased URL will be content/2010/02/01/my-new-content.


 

Displaying Popular Content In Drupal

The list of popular content is not a new feature in websites nowadays. By using the list of popular content in your website, you and your visitors will know which articles are read mostly by the visitors. In Drupal, displaying the popular content can be done relatively easy. You just need the Statistics and Views modules. The Statistics module is already bundled with Drupal and the Views module can be downloaded from http://drupal.org/project/views.

Prepare The Modules

You can follow these steps to prepare the required modules.
  1. Download Views module from http://drupal.org/project/views.
  2. Extract it to to sites/all/modules/ or sites/default/modules/.
  3. Log in to your Drupal website as administrator, then click menu Administer - Site Building - Modules.
  4. Enable the Statistics, Views, and Views UI modules, then save your configuration.
  5. Configure the Statistics module by clicking menu Administer - Reports - Access log settings.
  6. Enable the Count content views option, then save the configuration.

    Node counter
Build The View

You can follow these steps to build and customize the view.

  1. Click menu Administer - Site Building - Views.
  2. Enable the popular view.

    Enable popular view
  3. This view is ready to use now. But, I want to make some modification from its default setting. So, I click on the Edit link.
  4. I want to modify the Popular (block), this block will display list of popular content all this time, so I click the Popular (block) tab.

    Edit popular block
  5. In the Basic settings part, I click on the Use pager value (in picture below the value is Yes).

    Edit basic setting

    Scroll down the page. In this form, I choose No because I don't want to use pager. Then, I click the Update button.

    Edit pager
  6. I also change the Items to display to 10 and More link to No. The way to do this is same like the previous step.
  7. I don't want to display the total views number in the list. So, I click on the Node statistics: Total views from the Fields part.

    Edit fields

    Scroll down the page. In this form, I give a check on Exclude from display then, I click the Update button.

    Exclude field
  8. I only want to display the node with type blog. So, in the Filters part, I click on the + (plus) sign.

    Edit filters

    Scroll down the page. In the form like this, I give a check on Node: Type option then, I click the Add button.

    Filter by node type

    Then, the form like this will appear. I choose the Is one of option and check the blog checkbox. After that I click the Update default display button.

    Choose node type
  9. Click Save button. Now, this view is already customized just like what I want.
 Display The Block

Now, we just need to display that view as a block.


  1. Click menu Administer - Site building - Block.
  2. Scroll down the page and search for Popular content block. There might be two blocks named Popular content. Only one of them is the view that we have created before, and the other one is the block from the Statistics module. You can check it by enabling both of them. The one we have created before has no "All time :" letters in its content.

 

Wednesday, October 6, 2010

Multilingual Taxonomy

The Taxonomy translation module (part of the Internationalization package) provides multiple options to translate taxonomy vocabularies and terms. For each vocabulary you'll have to choose one of four different modes defining 'multilingual' behaviors for the vocabulary:
  1. None. No multilingual options for this vocabulary (default)
  2. Localize terms. Terms are common for all languages but their name and description may be localized.
  3. Per language terms. Different terms will be allowed for each language and they can be translated.
  4. Set language to vocabulary. The vocabulary will have a global language and it will only show up for pages in that language.
When a language is set for a vocabulary or term, only those that match the the current language will appear in taxonomy listings and when creating and editing nodes. If the language is set for a vocabulary, all the terms in that vocabulary will be automatically set to that language.

Per language terms

Creating terms with language is simple with the internationalization package. For example, we created the vocabulary 'colours,' which has no language assigned to it, thus allowing terms in multiple languages within the same vocabulary.

Figure 1: Creating a vocabulary that will allow multiple language terms within it.
Creating multilingual terms
Figure 2: Creating a taxonomy term with English language.
Then we created the terms 'red', 'green', and 'blue' in English and 'rojo', 'verde', and 'azul' in Spanish. If we go to the 'Translation' tab and click on Add translation, we can choose a term for each language that will be part of this translation.
Translating terms
Figure 3: Creating term translations.
If we repeat this process for the three terms, we can see all the translations in the Translation tab
Term translation tab
Figure 4: Term translations.
Once we have terms and translations, only the correct terms for each language will show up while browsing the site. When we are editing a node, the terms for that node's language will be available.


Friday, October 1, 2010

Use of i18n module to creae a multilingual website

    Hey wants to see your website in different laguages then  follow these
                         simple steps... :)


    1. First of all install a module called "internationalization" from the
        folloing link http://drupal.org/project/i18n follow the same steps to
        enable the module in admin/build/modules but dont forget to enable the
       "Locale module".


    2.After installation of module add language which you want,let we want
       our site to be in english and hindi,so we need to add hindi language go
       to the following link and add the hindi language "admin/settings/language
       /add".


   2.Now you are ready,the module you have installed will create a block in
       admin/build/block named as "language   switcher", locate it where you
      want.let we place it  in 'right sidebar'.


    3. configure the block, give it title etc..

    4.Now go to the link below,download and extract the 'hindi translation'
       package   http://drupal.org/project/hi

    5.This package will contain .po(portable object) files.


    6.Go to 'admin/build/translate',now you will see there are two languages
       english and hindi,below hindi there will be percentage of translated
       strings,zero now as we have not imported the hindi translation package.


    7.Now go to the import option(admin/build/translate/import) browse to the
       folder where you have put your hindi translation package.


    8.Import the files one by one to their respective text group for eg-import the
       module files in built-in-interface and profile files in profile text group.


    9.As you will import the .po files the percentage of translated string under
      hindi language will increase.


   10.To check your site is changing to hindi language or not go to language
       switcher in the right sidebar and click hindi,you will see your site in hindi :)


   11.Now you could see the full site is not in hindi language,this happens
       bacause till now we have imported the .po files for only the core modules
       functions,but we have also used the contrib modules for  them go as follows..
 

   12.Go to sites/all/modules and click any modules you will see a folder named as
       "translations"  open that folder and copy any .po file.


   13.Rename that file with 'hi.po'(this is for hindi translation),open file you will
        see a set of string with title as 'msgid' and 'msgstr'.


   14.Now copy the string from 'msgid', go to google translator convert this to
        your desired language and paste the converted string in msgstr title do it
        for whole file.


   15.Repeat this for all the modules you have installed.


   16.Now import these files as previous (admin/build/translate/import).


   17.Thats all now your site becomes bilingual....  :)