| Author |
Message |
|
| Guy |
 Posted: Thu May 17, 2007 1:42 am |
 |
|
Site Admin
Joined: 19 Feb 2007
Posts: 21
Location: Alameda, CA
|
|
| Back to top |
  
|
| francoisespurling |
| Posted: Tue May 29, 2007 5:34 pm |
|
|
Joined: 20 Feb 2007
Posts: 10
Location: London
|
| The guidelines would be very similar for a website but to obtain the best results, you will need to define your market clearly, not just in terms of language, but also in terms of geography. If only parts of the web site are to be localize, these should also be clearly identified. |
_________________
Françoise |
|
| Back to top |
|
| Guy |
| Posted: Tue May 29, 2007 7:14 pm |
|
|
|
Site Admin
Joined: 19 Feb 2007
Posts: 21
Location: Alameda, CA
|
| Is there anything that should be included in a web localization kit that is not common in a "regular" software localization kit? |
_________________
-----
Guy Smith
Silicon Strategies Marketing
630 Taylor Avenue
Alameda, CA 94501
510-521-4477
guy.smith@SiliconStrat.com |
|
| Back to top |
|
| francoisespurling |
| Posted: Tue May 29, 2007 7:36 pm |
|
|
|
Joined: 20 Feb 2007
Posts: 10
Location: London
|
| Not really. Software products vary a great deal and so do websites. If localization of sound was involved, for example, it would be helpful to include an audio script in the loc kit; however this applies equally to a software environnement or a website. All the building blocks found in software can be found on a web site. |
_________________
Françoise |
|
| Back to top |
|
|
|
