Which encoding is your source file saved in? Are you using a proper encoding for it AND a proper QString decoding method for building the string you pass to QRegExp ctor, like QString::fromUtf8? For instance, you can save the source file as UTF8, or save it as ASCII and put the unicode encoding of those characters, like “\xc4\x85” for the literal “ą”.

If you want everything between two quoatation marks you can use a simpler regex:

This matches if at least one character is between quotation marks.

Also, what’s the single backslash before your quotation mark in the regex for?

thank you Volker again, yours solutions is perfect :)

Volker wrote:

Also, what’s the single backslash before your quotation mark in the regex for?

1. # "\\\"[A" in C/C++
2. # is actually
3. # \"[A

When I looked in to QRegExp example, most of examples was started with “\\” so I thought that in my case it’s must to be, and it works except national letters ;)

Peppe, I almost forgot about encoding QString and this was a problem ;) eh, still I am amateur, thanks for anwser, next time I will be remember to encodnig QString ;)

Note that you can get around most encoding issues by using the hexcodes instead for symbols outside the standard character range. That is less readable, but probably more relyable. The problem with text files (including source files) is that they carry no information on the encoding they are in. That means that trouble can arise as soon as somebody else, unaware of your encoding settings, start editing your file.

thanks Andre for advice :) but if text files don’t carry inforrmations about encoding, how can I get this information? Suppose that in my apllication user can open every text file and content of this file is displayed on QPlainTextEdit, so I don’t have any chance to unearth innformation about encoding?

Nope, there is no relyable way. You can use some complicated routines that use some statistics or other heuristics to determine the likely encoding or something like that, but that’s not all that relyable. Just hope that UFT-8 will soon replace all other local encodings that are in use…

oh, it’s not good, but thanks for answer :)

Andre wrote:

Just hope that UFT-8 will soon replace all other local encodings that are in use…

If we write hex codes in sources no vendor will care for proper UTF-8 support in their products. Hexcodes are not the solution, they are the source of all that evil.

If you are thoroughly you can switch your entire code base to UTF-8 without problems in MS Visual Studio, Qt Creator and XCode.

Add to your .pro file

and to your main.cpp

This way you just can tell your code editors to open the files in UTF-8 mode if not stated otherwise. It works like a charm here in our team, involving different operating systems, programming languages and IDEs.

We are in year 2k11, in times of mega-supercomputing and what the hell has see, and I simply refuse strictly to type hexcodes in a file to gain an ‘ä’ or ‘ç’.

I am much grateful for this anwser :) This will be very helpful in my little project :)

f we write hex codes in sources no vendor will care for proper UTF-8 support in their products. Hexcodes are not the solution, they are the source of all that evil.