![]() Furthermore, it creates a folder structure for you where your source, bilingual and target files can be saved. While this may seem like the most tedious way of organizing things in the beginning – especially compared to using client project containers – it allows you to take advantage of advanced features and scale your activity for different, unknown needs (for example, outsourcing work to a colleague). It involves creating a separate project for each… project! A project has a definite start and end date and can have several files. This setup is for users who are familiar with CAT tools, handle multi-lingual projects, or involve multiple people in the translation process (e.g. Finally, you can create multilingual projects however, this feature is probably best suited for an organization involving unique projects (see below). Furthermore, you can add reference files to the project, such as a style guide. You can also create, add or import linguistic assets (TMs, Glossaries, Blacklists) and specify their location (unlike glossaries in WFP3). When creating a project, you can specify where you want to save the project to. This is also a set-up that most users used for WFP3. This would be a set-up for a freelance translator who has multiple clients and wants to keep client data in separate TMs. The pros and cons are the same as above, and the only difference is the user profile. This is basically the same as the above example except that projects are per language pair that you translate into and per client for example, Client ABC FR-EN and Client ABC ES-EN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |