Ivan, it is very simple.
The original discussion thread about issue-#19 is already closed, so it is clear that we need a new discussion thread.
I would simply use the same number but a more specific title e.g.
"issue-#19 wrong encoding ...".
Can we rename the existing thread that way?
The voting is then also entitled "issue-#19 wrong encoding ...".
Thereby you can later easily search for "issue-#19 " in the forum
or for "Refs. #19." in git.
But we don't need another issue in redmine.
This is the simplification!
Note that the list of issues in redmine is the set of issues that constitute the changes from 1.6 to 1.7.
A change inside 1.7 development steps is not required to be documented in the list of issues
that describe the changes from 1.6 to 1.7.
By using the same issue number we group together what belongs together.
It just happens to be split to multiple merges (and votings) because we are not smart enough
to get everything right at the first shot.
Regarding the Kernel versus Strings stuff:
The Utf8/Unicode Kernel operations in DevBrowser have been introduced in issue-#19
and they are inappropriate, so they are now corrected within issue-#19.
See the discussion of HostPackedFiles (
http://forum.blackboxframework.org/view ... =250#p2236)
for an example where it is justified to bypass Strings and use Kernel directly.
This must be the exception, not the usual case.
Using Kernel must be avoided if there is an alternative and if there
is no strong argument for justifying an exception.
- Josef