Open dieskim opened 6 years ago
will test asap.
@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.
@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?
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
separator12
Steps to reproduce the issue
Expected result
Actual result
Additional comments