More rephrasing.

Philippe Tourigny 2022-08-26 22:51:08 +09:00
parent d9fc295b98
commit 5cddede514
1 changed files with 11 additions and 15 deletions

26
Home.md

@ -2,41 +2,37 @@
This repository is simply a collection of small, but hopefully useful scripts, used to make working with various CAT tool-related files easier.
At the same time, it is also meant to provide a learning space in my programming journey, with this wiki serving to chronicle that journey.
At the same time, it also constitutes a learning space for my programming journey, with this wiki serving to chronicle that journey.
While I am merely a dabbler, I have made an effort to follow best practices to the best of my understanding. I hope that this repository can serve the secondary purpose of demonstrating the usefulness of even minimal programming knowledge to other translators (or anyone else with a non-computing background), and both inspire and help them on their own journeys.
While I am merely a dabbler, I have made an effort to follow best practices within the limits of my understanding. I hope that this repository can serve the secondary purpose of demonstrating the usefulness of even minimal programming knowledge to other translators (or anyone else with a background in languages or the humanities), and both inspire and help them on their own journeys.
## Background
A number of years ago, I managed to gradually introduce _OmegaT_ in my workplace and slowly wean my fellow translators away from the primitive approach of typing translations directly over the text in a copy of the original file sent by the customer to using a computer-assisted translation (CAT) tool.
A number of years ago, I managed to gradually introduce [_OmegaT_](https://omegat.org/) in my workplace and slowly wean my fellow translators away from the primitive approach of typing translations directly over the text in a copy of the original file sent by the customer to using a computer-assisted translation (CAT) tool.
The change in workflow resulting from the use of _OmegaT_ also led to more opportunities to automate various pre- or post-processing tasks needed to make efficient use of CAT.
The change in workflow resulting from the use of _OmegaT_ eventually resulted in opportunities to automate some of the pre- or post-processing tasks needed to make efficient use of CAT.
The first scripts and macros ([described here for the curious](https://codeberg.org/Kazephil/Little_CAT_Tools/wiki/Detailed_backstory)) I wrote centered around highly specific tasks targeting specific jobs. Over time, however, I also wrote a few scripts with more general applicability. They tended to be written linearly, with user names or similar information hardcoded into the scripts, and a lot of duplicate code copied and pasted from one script to another (most notably the code to bring up a dialog to select a file or folder).
My first scripts and macros ([described here for the curious](https://codeberg.org/Kazephil/Little_CAT_Tools/wiki/Detailed_backstory)) centered around highly specific tasks for jobs with a narrow focus. Over time, however, I also wrote a few scripts with potentially more general applicability. They tended to be written linearly, with user names or similar information hardcoded into the scripts, and a lot of duplicate code copied and pasted from one script to another (most notably the code to bring up a dialog to select a file or folder).
Essentially, the scripts were cobbled together in a hurry to address an immediate need, with the intention of going back and cleaning them up "when I had time".
Unfortunately, a change in management and organizational structure then imposed the replacement of _OmegaT_ with _memoQ_ on us before I ever found the time to go back and refactor my scripts. (The forced transition ended up inspiring an additional script, though).
Unfortunately, a change in management and organizational structure then imposed the replacement of _OmegaT_ with _memoQ_ on us before I ever found the time to do so. (The forced transition ended up inspiring an additional script, though).
The scripts went into limbo, half-forgotten for a few years. However, I still remained interested in programming, and have been attempting to extend my (meagre) skillset to Java by joining [a (very) casual group of people interested in exploring the OmegaT code](https://git.sr.ht/~brandelune/omegat-as-a-book).
The scripts then went into limbo, half-forgotten for a few years. However, I remained interested in programming, and have been attempting to extend my (meagre) skillset to Java by joining [a (very) casual group of people interested in exploring the OmegaT code](https://git.sr.ht/~brandelune/omegat-as-a-book).
I still prefer _OmegaT_, and find myself wishing I could go back to it at work on a daily basis, and still occasionally use it for personal purposes at home.
I still prefer _OmegaT_ as a CAT tool, and find myself wishing I could go back to it at work on a daily basis, and still occasionally use it for personal purposes at home.
As luck would have it, I've also been assigned secondary duties that involve working with another company, and I can use _OmegaT_ for translation tasks on their computer.
I therefore decided to go back to the concepts behind those scripts and challenge myself to completely rewrite them from scratch as more general-purpose scripts.
The result is this repository.
I therefore decided to go back to the concepts behind those scripts and challenge myself to completely rewrite them from scratch as more general-purpose scripts, and make them available to others.
## An Ongoing Journey…
I hope to build on the initial foundation represented by this repository and Wiki in the following ways:
I hope to build on the initial foundation represented by this repository and wiki in the following ways:
1. At the code level:
- Follow-up on the potential todo items listed in the scripts to further improve them.
- Write other little tools, not necessarily limited to targeting _OmegaT_, that can help translators with various pre- or post-translation tasks.
2. At the Wiki level:
2. At the wiki level:
- Write documentation describing the requirements and usage of the individual scripts.
- Add detailed explanations of each script describing the chosen approach and its reasoning, as well as how it works, for the dual purposes of consolidating my own knowledge and, hopefully, helping other translators trying to learn how to code who stumble on this repository.