Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
| > I have been making small progress on the unicode branch
| > (svn://svn.lyx.org/lyx/lyx-devel/branches/personal/larsbj/unicode),
| > but the work is comming along really slow.
|
| Lars, looking at the patch that Georg posted I see stuff like
|
| + std::vector<char_type> str;
| + str.push_back(par_.getChar(pos));
| ...
| + pain_.text(int(x_), yo_, &str[0], str.size(), font);
| + x_ += font_metrics::width(&str[0], str.size(), font);
|
| So, is the plan to use a std::vector<char_type> as the data container and to
| pass char_type* to functions that manipulate these data? What will happen to
all
| those functions that currently handle std::string? Do they get changed to
| std::vector<char_type> too?
I think we have to, yes.
| On a more practical level, why not define a
| typedef std::vector<char_type> lyx::string;
Or perhaps a nother name. (ustring, docstring suggestions welcome.)
But yes, we could/should do that.
--
Lgb
