It requires modifying source files and recompiling. There is no good way to inject translation variants otherwise, because we want the full analysis in the context.
So, add all the variant words to the dictionaries, with the desired alt="" parameter. Add the variant to the Makefile.am files and preferences CG-file. Build the languages and pairs. Run the translation with the desired variant in AP_SETVAR environment variable. Beyond that, ask the mailing list. I haven't worked with these systems myself, but I would say the wiki page explains it rather thoroughly, and there are example languages/pairs to look at. -- Tino Didriksen On Thu, 27 Feb 2025 at 14:51, Sergio Martinez <sergio.martinez...@gmail.com> wrote: > Thanks for your extremely fast response. > > I did read the documentation, but unfortunately, after looking at it, I am > still struggling to achieve the desired results. Specifically, I explored > both the dialectal/standard variation and translation memory solutions, but > I can't see the full context to address my use case. > > Would you be able to offer a more specific guideline on how I could > integrate user group-based variations in the translation process? For > example, could I create a specific modes.xml/pipeline based on user group?, > or is there another strategy that could help achieve this kind of > functionality? > > Any insights you could provide would be greatly appreciated. > > El mar, 25 feb 2025 a las 12:43, Tino Didriksen (<m...@tinodidriksen.com>) > escribió: > >> [CC: apertium-stuff mailing list] >> >> Your question is almost identical to one I answered a week ago. The >> answer was: Yes. That can be done with either >> https://wiki.apertium.org/wiki/Dialectal_or_standard_variation (best >> option) or https://wiki.apertium.org/wiki/Translation_memory >> >> -- Tino Didriksen >> >
_______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
