Initial Site Structure

Its up to you to say which part of your site is to be multilingual. You do this by defining a category for the mother language somewhere, anywhere , in your site structure. linguist Plugin cannot do it because it doesn't know where you want to put it. Often you will want urls for your site such as

Relative path	Notes
/	(home page)
eng/	category for English
haw/	category for Hawaiian

which you can do with a site structure like this

	<hierarchy>
	  <story name="Home" pathname="" msgNum="1"/>
	  <category name="haw" pathname="haw" msgNum="7"/>
	  <category name="eng" pathname="eng" msgNum="8"/>
	  </hierarchy>

but you may only want part of the site multilingual.

Relative path		Notes
/		(home page)
dir2/		directory with multilingual sub directories
dir2/	haw/	category for Hawaiian
dir2/	eng/	category for English
dir2/		directory without multilingual sub directories

which is done with a site structure like

	<hierarchy>
	  <story name="Home" pathname="" msgNum="1"/>
	  <category name="Multilingual Subsite" pathname="dir1" msgNum="6">
		  <category name="haw" pathname="haw" msgNum="7"/>
	 	  <category name="eng" pathname="eng" msgNum="8"/>
	 	  </category>
	  <category name="Monolingual Subsite" pathname="dir2" msgNum="6"/>
	  </hierarchy>

Because of this freedom , linguist can only proceed when the location of the mother tongue language code catgeory is known. The Managing Editor must add that one category to the site structure and linguist will do the rest.