Number Settings - Thousands Separator gets reset

Question

We are having a problem with Number Settings. The team has chosen to use a space as the Thousands Separator, so numbers appear as 12 000, etc. The default seems to be no Thousands Separator, so 12000. With this default, our numbers with spaces appear as errors: “Invalid leading zero: 000” . As Administrator, I change the Thousands Separator to a space " ", and then rerun the check, and the errors disappear. Then I do a send/receive to make sure that setting gets shared with the team, and if I rerun the check again immediately after that, I get the number error again. Opening the Number Settings reveals that the Thousands Separator has gotten reset to the default of no separator. I tried this on a test project, and got the same result, so it’s not just our project. Also in my test project I tried it with a Thousands Separator of “,” and it didn’t get reset after a S/R. So it appears that Paratext doesn’t like a Thousands Separator of space, at least when it is doing S/R.

Should I report a problem from within Paratext, or is this post sufficient?

Answer 1

Please report this inside Paratext in case there is more information in the log file.

Answer 2

I sent in the problem report. Someone suggested offline that I use a non-breaking space. Actually, the non-breaking space doesn’t seem to be remembered as a separator through a S/R either. Furthermore, even if non-breaking space worked, I would need to use the Paratext non-breaking space special character, e.g. “12~000” (as that’s the only way that Paratext seems to remember a non-breaking space). I don’t think it is very helpful for the team to see “~” characters scattered through the text, so we have just used spaces in the text, and fixed them to non-breaking spaces in the typesetting.