On Tue, Oct 23, 2007 at 05:31:29PM +0200, Georg Baum wrote: > Uwe Stöhr wrote: > > > >> I couldn't get to make .find() work with docstrings. > > >> Could you implement this? > > > > > > No time. But docstrings work exactly like std::string, so you should > > > not need to do more than changing the types string->docstring and > > > char->char_type. > > > > This is what I did but I get then a huge list of compilation errors. All > > of them complaining about that lyx::chartype can't be converted to char. > > That does not work on purpose. If you are 100% sure that the chars in > question are pure ASCII you can use a simple cast from char to char_type > (as done elsewhere). Otherwise you need to use some of the encoding > functions. Or the error messages indicate that you still need to change the > type of some variables to docstring. > > > >> > Besides, this is a file format change and needs lyx2lyx support. > > >> > For example, a previously escaped "\%" needs to be changed to an > > >> > unescaped "%". > > >> > > >> No, the LyX-file itself is not touched, only the LaTeX-output. > > > > > > Not long ago a change like this required a file format change. Are > > > users now supposed to do the unescaping manually? Or should they live > > > with the fact that a file that previously had a "%" in a url now has an > > > additional backslash? > > > > As I wrote, former URL insets are now URL styles where the characters are > > treated as before - bug 449 is not yet fixed. I already incremented the > > fileformat: > > No, they are not treated as before. A "\%" in an URL style results now in > "\\\%" in .tex file, previously it resulted in "\%". This is IMHO not > acceptable.
Not any more... if I enter '\%' into an url inset, it becomes \backslash % in the LyX file, and '\%' in the LaTeX file. Are you referring to before my last patch? > > >> I already committed lyx2lyx stuff: > > >> http://www.lyx.org/trac/changeset/20950 > > > > > > That is something else. > > > > This and Richards lyx2lyx stuff he committed 2 days later is exactly what > > is needed. URL inset is converted to an URL style. > > No, this is not all what is needed. See the discussion in the Userguide > thread from last week. > > > Georg - Martin
