About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community_call:minutes20230502

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
community_call:minutes20230502 [2023/05/02 13:49] – [2. Technical Discussion: Internationalization with localise] demiankatzcommunity_call:minutes20230502 [2023/05/02 13:58] (current) – [3. Open Q&A / Other Topics?] demiankatz
Line 115: Line 115:
  
 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? 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? ==== ==== 3. Open Q&A / Other Topics? ====
  
 +None this month.
 ===== Next Call ===== ===== Next Call =====
  
community_call/minutes20230502.1683035382.txt.gz · Last modified: 2023/05/02 13:49 by demiankatz