Breaking a line in two, generates error message "No space after custom character"

[Xenos Latinos]

Hi,

The only remaining issues that I run into while testing the new version 06, has to do with line breaks.

A minor issue, first:
When I load a file in which the first subtitle has two lines, then the error message "No space after custom character" is displayed for that line, in the Information and errors window. No error is displayed for all other line breaks in the subtitles after the first one.
If the first subtitle has only one line, no line breaks of the following subtitles are detected as errors.

Now the real issue:
When I hit ENTER to break a single line in two, either in an existing subtitle or while creating a new one, the error message "No space after custom character" automatically appears in the Information and errors window, for the specific subtitle. This happens for every subtitle I try to break in two lines. So, as I go on greating subtitles, the Information and errors window gets filled with these errors.

I checked again in 'Space after characters' in Tools -> Information and errors -> Settings -> advanced as you mentioned for the "Unnecessary spaces" issue, but still there is only a dash in that field, nothing else to indicate ENTER.
By the way, is it possible to add ENTER in those fields and if it is, how can I do it? I don't need it now, but just in case...

Editng the report, to add something I just noticed:
In a subtitle with two lines, when I change text formating (bold, ubderline, italics) of only a part of a subtitle (one or more words, but not the whole text), error message "No space after custom character" appears in the Information and errors window.
If I perform one undo, the error message dissappears, but the change to the formating is not undone.
With a second undo, the change to the formating is undone, but the error message "No space after custom character" appears again.
I hope this helps.

Thanks again for all your work on this great tool,
Xenos

[Kameleon_]

Hi Xenos,

I can not reproduce this error, probably due to a difference in settings.
Could you dive me your 'SubtitleWorkshop.ini' file? Thanks in advance.

[Xenos Latinos]

Hi Kameleon,

I'm so sorry for the false alarm...
I just performed a full uninstall of the new version (06) with a third party tool, reinstalled it and now everything is working properly. Who knows what I managed to mess up with all these tests.
Just in case you want to have a look, I copied the ini file before the uninstall and I've attached it below.
Feel free to delete the whole topic if you want, since the reported issue is non existing.
Again, I'm really sorry for any inconvenience.

Best regards,
Xenophon

[Kameleon_]

Thanks Xenos, I will have a look into yout .ini file.