View Single Post
Old 01-09-2021, 01:58 PM   #60
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,860
Karma: 6120478
Join Date: Nov 2009
Device: many
Again, for those following along, given the CSSParser appears to work on a wide range of input, I plan to convert CSSParser.cpp from std::string, std::map, and std::vector to use QString, QMap, and QVector, so that position information for each token matches the QString location used inside of Sigil. Current position information returned represents the position in a utf-8 string so it can not be used easily inside Sigil without a mapping of utf-8 offsets to QChar (utf-16) offsets in a QString.

I will keep the std::string versions in its own repo someplace for those interested.
KevinH is offline   Reply With Quote