Closed snomos closed 4 years ago
The initial default values should reflect the defaults we want for most languages, which are:
yes
is best as the initial default value.Another compilation option is alignment, but that one is already set to yes for all languages, and should probably just stay like that. If needed, we can add an option for that one later on.
And as mentioned above, we should just make the hfst-backend=foma as a default everywhere.
I have added a place for some default options finally. sorry for the delay I had to tread carefully for the first template merge.
For the larger theme of making the infra more like any modern software engineering project / framework, it is my long term goal as well.
As for XFST, in the case of crk, the XFST implementation of TWOLC, the twolc
compiler, did not work properly with the morphophonology, so we have had to hfst-twolc
. In the case of srs, the XFST compiler xfst
breaks with twosided flag-diacritics
, so there as well we have had to use hfst-xfst
. Maybe XFST works as it should for other languages, and it certainly is faster than HFST, but since XFST is known to not to work, I'm not convinced we really should be promoting its use at all anymore.
As for XFST, in the case of crk, the XFST implementation of TWOLC, the
twolc
compiler, did not work properly with the morphophonology, so we have had tohfst-twolc
. In the case of srs, the XFST compilerxfst
breaks withtwosided flag-diacritics
, so there as well we have had to usehfst-xfst
. Maybe XFST works as it should for other languages, and it certainly is faster than HFST, but since XFST is known to not to work, I'm not convinced we really should be promoting its use at all anymore.
I suggest we move such general discussions to Zulip. I will reply there.
It would be useful to have a section in
configure.ac
to set language specific compiler and optimisation options. Relevant options are:The idea is to define a section with suitable variables in
configure.ac
and then reference these variables in the relevant places in them4/*.m4
files. This way we can tune the default compilation options for each language, while at the same time keep the general configuration files language independent.This was first discussed in giellalt/lang-crk#3.