Allow Empty / Blank Strings - Dont re-load origin string if string saved as empty about com_localise HOT 4 OPEN

will test asap.

from com_localise.

@dieskim

I confirm your findings. Not sure we should consider it as an issue.
A simple way to get rid of the problem in your case is to enter a space in the field.
In this case, com_localise will consider the field as translated.

from com_localise.

@infograf768 - yes I can use a space, but then the space gets output in the actual output code, and this can at times get pretty ugly, espessially if you have two or 3 language strings next to each other

If for Example:

$chapterTitle = JText::_('COM_CHAPTER_TITLE_PREFIX_SEPERATOR') . JText::_('COM_CHAPTER_TITLE_SEPERATOR') . JText::_('COM_CHAPTER_TITLE_CHAPTERNAME') . $chapterNumber;

In something like that you will now have 3 spaces if we have to use spaces - then the $chapterNumber - but if we use blank(null) we can use any combination, 1 , 2, 3 or non and have no spaces.

A simple fix would be to add a global config that we can enable to ignore and not reload blank values?

from com_localise.

I then suggest you use ​ the zero width space: https://www.fileformat.info/info/unicode/char/200B/index.htm in the field. It should work for your needs.

I used it below between separator and 12

separator​12

from com_localise.