I would like to get feedback on this design change decision in ox-hugo related to this auto-fill behavior.
The change in https://github.com/kaushalmodi/ox-hugo/commit/ad9eb052033f196597e82b23c426d6b887156f60 caused a regression for ox-hugo users using multi-byte chars other than Chinese.
I realized that after this bug report: https://github.com/kaushalmodi/ox-hugo/issues/300 .
I am not surprised seeing that bug report because that auto-fill behavior change is not common in the multi-byte char scripts I know of too: Gujarati, Hindi.
So, would it be OK, If I enable the autofill behavior in the above mentioned commit only if
#+language: zh is set in the Org file?
I think that would be much simpler and performance efficient than using regular expression to parse if the multi-byte char fits in the Chinese char range of unicodes. I will also make that an elisp variable that can hold a list of strings, so that people can add more language codes to that list.
/cc @Tisoga @Kathy_H @yssource