adding ',0' to a .db line still triggers warning

[CableGuy67]

With a .db that has an odd number of characters adding ',0' should be respected or counted. Instead the warning,

Warning : A .DB segment with an odd number of bytes is detected. A zero byte is added.

is issued. Considering that the line looks like,

.db "ud*",0

either the counting is off or zeros are being added willy-nilly. Is it possible the ',0' isn't being looked at?

EDIT: this one is wrong. It does work fine. It seems to only be the ones with single tick marks in them that can't be fixed by adding the ",0" to the .db line.

[CableGuy67]

To follow up on this it seems there is a problem with the single quote (tick). It is used for a couple of the Forth words and it's like the line isn't being counted, just saying it's adding a zero. The words exist in the dictionary but something is most certainly amiss. I'm am currently using the fork of this that fixes a few things like spaces around parens for macros and case problems with the X, Y, Z registers. It is the development branch listed for issue 45 and others here. It does allow AmForth to be built now which is great. Just these smaller issues.
I can't seem to find where the single paren thing is happening. It's most certainly the issue though. Probably just because why would a word have a tick in it. Forth.