Problem with Serbian Latin letters

Hello,
Since it was released version 8, have a problem with displaying Serbian letters.
This problem did not exist in version 5th.
Here's a picture attached which shows how one looks in version 5 and one in the current version.
MySQL version is 4.1.22.
Thank you.

I'm sure the developer will ask the for the table definition and maybe an hex dump of a sample cell—you can use MySQL's HEX() function for the latter.

Ok,
in attach is picture of table structure, and here' s HEX of Serbian Letters:

Letter HEX
ć C487
Ć C486
č C48D
Č C48C
đ C491
Đ C490
š C5A1
Š C5A0
ž C5BE
Ž C5BD

The most important column "collation" is hidden in your screenshot. Please paste the CREATE TABLE query which you have in the "Create code" tab.

A table with default collation "latin1_swedish" and serbian characters?

CREATE TABLE `account` (
`accountid` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,
`name` VARCHAR(150) NOT NULL DEFAULT '',
`code` VARCHAR(9) NOT NULL DEFAULT '',
`type` VARCHAR(255) NULL DEFAULT NULL,
`note` VARCHAR(255) NULL DEFAULT NULL,
`accountts` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`accountid`),
UNIQUE INDEX `code` (`code`),
INDEX `accountts` (`accountts`)
)
COLLATE='latin1_swedish_ci'
ENGINE=MyISAM
AUTO_INCREMENT=1465
;

Collation is "latin1_swedish".
At the time the database was created close to 2000 there was no other option and everything work perfectly.
But again Heidi version 5 all operate normally.

When I set a colation to latin2_croatian_ci, instead of Serbian letters I again receive various sings.
Picture is in Attach.

Apparently, earlier HeidiSQL versions incorrectly displayed e.g. 0xC5BD bytes in a Latin-1 string as the Ž character (U+017E). To begin with, Latin-1 is a single byte encoding—that byte sequence should be interpreted as two characters: 0xC5 (Å aka U+00E5) and 0xBD (½ AKA U+00BD). Additionally, Latin-1 doesn't have most of those chars you mention.

Of course, this doesn't explain why you get � (U+FFFD) instead of Ž. But older behaviour was definitively a bug in HeidiSQL.