|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Need ideas for website localization
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Need ideas for website localization
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Need ideas for website localization - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
tgr Member
|
We have just redesigned our website, and I found your news story about dogfooding quite intriguing. The main part of our website, we maintain in four languages. I addition there are sections of the web that we do not have the resources to keep updated in more than one language (e.g. technical articles). For these pages we just need the new text to be copied to the other language sections whenever the master page changes. I would love to learn from your experience in running your web project. What is the setup, and how is the flow when updating the pages? Anything we should keep in mind? Thanks, Trond
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Trond, Our concept is to store every localized web in an own local folder since we use different web servers for each. Our batch does the following: a) copy all changed files from the original folder to the language folder. Now we have two exact copies. b) use SLMake to build the localized version of the web. It overwrites the copies of the original with localized versions. We used localize similar files in a folder for all files but excluded the paths with stuff not meant to be localized. c) the last step synchronizes all files in the localized folder using ftp. We took care that pictures did not hold text so did not need to localize them. Instead we placed text above the pictures. We also planned in a way that we keep untranslated parts togehter in path so our list of exclusions can hold complete paths and not files. Our php scripts all have files with declares with all strings in it. We excluded all php scripts from localization of the similar files but added the language files to the project using Project - Add Source. If we change stuff in the original we open the GUI to scan for changes. Then the translations are done. If they are complete the batch above is started. Copying all changed files in step a makes sure that pictures are updated, scripts are fresh and config files are up-to-date. Step b makes sure everything meant to be translated will be translated. And c publishes the stuff. That all needs a bit preparation like to avoid text in pictures or grouping files in folders meant to translate or not. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
tgr Member
|
Hi Markus, Excellent! Just what I wanted to know. I think this metod could work for us. Btw, I believe this would be a great theme for a blog article. My guess is that a lot of users ar not aware of how elegant this can be set up. Thanks, Trond
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Trond, Some parts of a localized website need to run on the server of the original language. In our case this is our Update Alarm form which has to share the same database everywhere. We used IFRAME tags for that. The trick is to bypass the top level domain to the script running in the IFRAME so it can display itself in the right language (while running on the .com server). You are right, we should make a blog article from it. In the very next step we eat a bit more dogfood and prepare the next language version of our website. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
tgr Member
|
Some parts of a localized website need to run on the server of the original language. In our case this is our Update Alarm form which has to share the same database everywhere. We used IFRAME tags for that. The trick is to bypass the top level domain to the script running in the IFRAME so it can display itself in the right language (while running on the .com server). Interesting, we may need to do something similar. We have the language code in a cookie, so it can be used as a parameter whenever needed. Thanks, Trond
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:10 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Need ideas for website localization | |
Sisulizer software localization tool - Three simple steps to localize
