|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Sisulizer at Enterprise level - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Daan Krijnen Member
|
Hello, I am working at a large company with locations all over the world. At the moment we are using Sisulizer for two projects. One webbased and one in C#. The questions: How do we organsize Sisulizer with project files, etc if we want to expand the use of Sizulizer to all projects. Basically to be able to re-use translations and translated phrase one time and be able to check and use "Company translations" in all projects. Can somebody advice us on this issue?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Daan, one possibility is to use Sisulizer Enterprise for developers and Sisulizer Translator Edition for the translators in your company and exchange translations with the translation memory. Both editions can store and use translation on a central SQL server. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator 
|
This solution give you possibility to exchange between projects and your translators on whole world in real time, and it seems to me best solution for your company, but Sisulizer is flexible software and allows on many different translation exchange ways, for example you can also to create your own repository files system by export translations from your projects to CSV or TMX files. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Daan Krijnen Member
|
Hello, Thanks for the replies. We allready use Enterprise edition in combination with the Translator edition in the projects. Do you have some guidelines/manual/paper how to set up and configure an SQL-server in combination with Sisulizer as mentioned? TIA
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, You can to find some useful information about how create New Translation Memory here: http://www.sisulizer.com/online-help/NewTranslationEngineDialog.htm Of course, If you have additional questions, we answer with pleasure on your questions via forum. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Daan, this is very simple in Sisulizer. Use Tools- Translation Engines... There click the left green + button to add a new engine. Select "Sisulizer translation memory on SQL Server database" (or my SQL/Firebird...). Connect to your SQL server with the settings in Database. You need an account on the server that can create and change tables on the server. Use the same server and database in your Translator Editions. The translators need an account to read and write on your server. After you connected and closed the dialog you should move the new engine to the top of the list in the Translation Engines dialog (the one where you pressed the green + button). It is the list to the left. Use the arrow buttons to move it up the list. USe File - Save to Translation Memory to update your database. Use Project - Translate using Translation Engine to re-use the translations. Markus Attachment: 0106.JPG (Downloaded 45 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Daan Krijnen Member
|
Hi Marcus, That looks easy, connecting. How do I configure the database itself? Or does Sisulizer do that for me, after connecting?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, you need an account to your SQL-Server and the right to create tables in a database. This is a bit different for each server type. Sisulizer will add the needed tables to an existing database. It is really that simple. But of course you need to have basic knowledge on how to maintain and use your SQL Server - or you ask your database administrator. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Daan Krijnen Member
|
Hi Markus and Januzs, I think I got the basic picture: - We take a SQL server as a translation engine; connected as described above. Off course you have to create a new database. (I know how ... I familair with databases.) - Once a new project starts, you add all your source files you want to translated. Use the option translated using translation engine and it translates all items in the project which matches the ones in the database - You can use save to the translation memory to put new Items in the database. Is this correct?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Yes, that is the idea behind it. It is useful if you work in a team at the same time at the same language pairs, e.g. three translators doing EN - DE translation at the very same time. If you have three translators translating e.g. EN-DE, EN-FR, and EN-IT then they will not profit from it too much. As Janusz mentioned you can also import and export existing using TMX (File - Import/Export). This is sometimes simpler and faster. You would import your translations from your TMX once you started a new project. If you have just one project but with many sources you can use Project - Add Source... to add them to the same project. This way you can use the automatic translation of duplicates or use Project - Translate Duplicates. Of course you can still exchange using TMX or translation memory if you use a project with many sources. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Daan Krijnen Member
|
OK! I think we have lots of possibilties here. In our case lots of software building projects are going on, all over the world. All these projects are responsible for translations of their software into 5 other languages. How and esspacially who is doing the translation is up to the project. Most of the time a member from the usergroup attached to the project from the original country is doing the translation. What we can do know is the following: - Set up a company wide database (do we need different ones for different languages?) with translation - Import already finished projects into the database. (Their are only a few) - Educate all other projects how to execute translations with the use of the database and Sisulizer. Sounds like a working scenario? Do I miss some points to consider?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Daan, this sounds more like a classic scenario. Simply create one .slp and use it as a sort of a master project. Then you use the exchange wizard to send the translation packages to your partners. If they send back to your their .slp you import it to your master and you have a complete set of translations. If you start a new project for a different software you can import your strings from the older .slp (use By Value while the context of the strings must be different in such situation). You can also use translation memory for this task. But importing from .slp is sometimes faster and easier. A shared TM on a SQl Server makes only sense when all users have access to it. It can be a lot of administrative work to build-up a world-wide database access. Sometimes it is easier to go the simple way. Shared TM is a good choice if you want to speed up translation and hire two or more translators for one language pair who are in one office. For quality reasons it is better to give one language pair to one translator at one time. This is the best way to get a consistant usage of terms. Sisulizer has a lot of ways to re-use existing translations. You will not loose your translations :-) Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Daan Krijnen Member
|
Hi Markus, Need some advice here: Using and exchanging .slp files creates an enormous problem keeping track of all those files. As I said we do not know who is doing translation and therefore needs them world wide. (Scope: We are located in 200(!) countries; software devolpment is organised more central but still in more then one country and involvement of the business itself, like in a usergroup is organised from lots of different countries) I think its is easier to manage the acces the central database for a project, (as we already manages all access to applications centrally) and providing projects guidelines how to set-up translations in stead of sharing all those .slp files. Other scenario can be getting translations out of project and organize them centrally. Problem is that for good translations of software you need knowledge about the software and the process around it. Therefore it is done within the project and I do not think it will change ... But maybe I am overlooking things here ...?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Daan, with a Translator Edition in your branches for the languages you can decentralize the task. You send the slp once to each branch. They use Project - Scan for Changes to update their project to the newest release of your binaries (this would use the internal TM to re-use translations). With the possibility to build the target your branch would be independend. The newest version of your software you have to distribute to your branches in any case, so there is no change. And with the Translator Edition you do not need to send back the .slp to the master project. What do you think about that? Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi Daan, Excuse me my late reply, but I was whole day out of office. Markus perfectly explain capabilities localization work with Sisulier, but I have also some hints. Set up a company wide database (do we need different ones for different languages?) with translationTranslation memory can contains many different language pairs, below is screenshot of example TM properties, red rectangle indicate language pairs set in TM. Of course you can use many translation memory with Sisulizer (red narrows on screenshot indicate various TM), e.g. for selected projects, languages etc. and of course, each translation memory could based on different database engines e.g. MySQL, DBISAM, SQL Server, Firebird. Attachment: screen.png (Downloaded 29 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
with a Translator Edition in your branches for the languages you can decentralize the task. I agree with Markus. It seems to me that projects exchange system based on Enterprise and Translation edition is better than centralized TM because is more flexible, SL allows on many different import/export method - you should to test it individually and e.g. go through all steps of Exchange Wizard (on screenshot below), this solution haven't also some limitations of TM solution (e.g. max string length). Additional for such big company one shared TM with thousands translated strings, many files, languages and many translators working online in this same time could exceed performance possibility of every SQL server. Unfortunately, exchange projects solution need good organization of exchange files and information e.g. by some smart FTP or web system based e.g. on modern PHP solutions. Best regards, Janusz Attachment: screen2.png (Downloaded 30 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Daan Krijnen Member
|
Ok thanks on the input and the tips. It will helps us to organize things around translation. Another question: Suppose we have decided that User always should be translated in French as Utilisateur How can we make sure that in new project by some control/import mechanisme the right translation of User is done? Last edited on Thu Aug 21st, 2008 11:23 am by Daan Krijnen |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Daan, this is a feature called terminology and it is already on our road map. In the moment you need a third party tool terminology tool to synchronize your translators. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 06:16 pm | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Sisulizer at Enterprise level | |
Sisulizer software localization tool - Three simple steps to localize
