Differences

This shows you the differences between two versions of the page.

--- community_call:minutes20230502 [2023/05/02 13:30] – [1. Development Planning] demiankatz
+++ community_call:minutes20230502 [2023/05/02 13:58] (current) – [3. Open Q&A / Other Topics?] demiankatz
@@ Line 93: / Line 93: @@
 ==== 2. Technical Discussion: Internationalization with localise ====
+André has been exploring the lokalise.com platform, which the Open Library Foundation uses for some of its projects. It imports languages from GitHub, makes it possible for users to collaboratively improve/expand them, and can then be configured to export data back into the project using pull requests.
+The interface displays percentage done, number of words in need of translation, and "unverified" strings that might have problems and should be reviewed.
+The system also has project management features built in, so you can assign work, create tasks, etc.
+Some quirks may confuse the project (e.g. @parent_ini directives, use of language codes that don't exactly match lokalise's expectations -- e.g. zh.ini had to be manually mapped to Chinese Traditional).
+During import, lokalise is currently set up to ignore native.ini -- this is a special file and would not benefit from management through the platform.
+Text domains are imported using filename patterns, which enables us to keep domain-specific strings appropriately separated.
+When translating, the platform automatically makes suggestions based on similar strings in the existing language files and using online translation tools, to help streamline the process (though of course, human verification/judgment is still needed).
+André opened a German-specific example pull request as a proof of concept. This reveals some problems we need to overcome:
+  * Some files are renamed (e.g. en.ini --> en_GB.ini)
+  * Some formatting is changed (e.g. strings with special characters are enclosed in single quotes; double quotes are removed)
+  * All comments are removed
+  * Numeric keys are dropped (a problem for the Dewey Decimal text domains)
+Possible solution: Custom processor -- the ability to create a REST endpoint for pre- or post-processing of translations. Well documented with examples provided. One question: can the custom post-processor be combined with the "post PR to GitHub" option, or are these workflows incompatible?
+We confirmed that our current lokalise account seems to support the custom processor.
+There was some discussion about how/where to implement and host the processor: one option would be to create a repository that exposes a Laminas module containing the processing functionality, and then install that into the public demo instance to make it accessible.
+Also discussion about where to get comments from: one option would be to have the API just pull the latest .ini files from GitHub using URL patterns (raw download).
+Volunteers to work on the project: Demian will set up a vufind-org GitHub repo to build the module and will help with deployment to vufind.org. André will help with development of the code.
+André will inquire about the "numeric keys" problem; Demian suggested a possible workaround (key prefix via custom processor) we can use if no proper solution is available.
 ==== 3. Open Q&A / Other Topics? ====
+None this month.
 ===== Next Call =====