You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently: The customization script launches a dialog where the use enters the URL (e.g. https://cat.capstan.be/OmegaT/index.php) from which OmegaT will fetch the custom files. The idea to develop this further was that we would have a different URL for each customization required, assuming we would need a different customization for each project. The PM would include that URL in the instructions of the project kit and then the user would to enter it in the customizer’s dialog to fetch custom files for that project.
However, since most of the custom files are not project-dependent, the updates for each project would be minimal.
• Tag definitions -> unless they become project-based in the meanwhile
• Merged TMs -> Done with cApps?
• Glossaries
Therefore, it makes sense to have one single customization script, and then another script that fetches certain project-specific assets or settings in the background.
This script will:
Run when a project loads.
Check whether the project has already assets, checking for existence of folder /tm/auto/memoryln
a. If folder /tm/auto/memoryln exists and contains tmx files, it stops.
b. If folder /tm/auto/memoryln is not found, or is empty, it continues.
Check whether a working internet connexion exists:
a. If none, warns the user: “You need to be connected to the internet to update your customization for this project. Close OmegaT, connect to the internet and open the project again.”
b. If found, continue to the next step.
Download and parse a properties* file (XML or Json) from a fixed address, which states the customization needed, its latest version, location, etc. for each container.
Extract the container from the project name (for each container in the properties, find the one of the current project -> provide example).**
Extract the language combination from the project settings.
Fetch path to the project, and close the project
Edit the OmegaT preferences (omegat.prefs) to update the custom tag settings
Edit the OmegaT project settings (omegat.project) to add links for reference TMs, based on the template name in properties, updated with the language settings.
Currently: The customization script launches a dialog where the use enters the URL (e.g. https://cat.capstan.be/OmegaT/index.php) from which OmegaT will fetch the custom files. The idea to develop this further was that we would have a different URL for each customization required, assuming we would need a different customization for each project. The PM would include that URL in the instructions of the project kit and then the user would to enter it in the customizer’s dialog to fetch custom files for that project.
However, since most of the custom files are not project-dependent, the updates for each project would be minimal.
• Tag definitions -> unless they become project-based in the meanwhile
• Merged TMs -> Done with cApps?
• Glossaries
Therefore, it makes sense to have one single customization script, and then another script that fetches certain project-specific assets or settings in the background.
This script will:
a. If folder /tm/auto/memoryln exists and contains tmx files, it stops.
b. If folder /tm/auto/memoryln is not found, or is empty, it continues.
a. If none, warns the user: “You need to be connected to the internet to update your customization for this project. Close OmegaT, connect to the internet and open the project again.”
b. If found, continue to the next step.
2* Example of Json properties: https://cat.capstan.be/OmegaT/project-assets.json
3** Logic to get container:
The text was updated successfully, but these errors were encountered: