On Monday 03 November 2003 13:41, Andre Poenitz wrote:
>
> > @@ -293,8 +370,8 @@
> > if (p.next_token().asInput() == "[") {
> > latex_inner_pos = p.getArg('[', ']');
> > switch(latex_inner_pos[0]) {
> > - case 't': inner_pos = "0"; break;
> > - case 'c': inner_pos = "1"; break;
> > + case 'c': inner_pos = "0"; break;
> > + case 't': inner_pos = "1"; break;
> > case 'b': inner_pos = "2"; break;
> > case 's': inner_pos = "3"; break;
> > default:
> > @@ -318,11 +395,11 @@
> > ss << '[' << latex_inner_pos << ']';
> > ss << "{" << width << "}";
> > handle_ert(os, ss.str(), parent_context);
> > - parent_context.check_end_layout(os);
> > - parent_context.need_layout = true;
> > + parent_context.new_paragraph(os);
> > parse_text_in_inset(p, os, FLAG_END, outer, parent_context);
> > handle_ert(os, "\\end{minipage}", parent_context);
> > } else {
> > + parent_context.check_layout(os);
> > begin_inset(os, "Minipage\n");
> > os << "position " << position << '\n';
> > os << "inner_position " << inner_pos << '\n';
>
> Does minipage really code its inner_position as 0 1 2 3 instead of 't',
> 'c', 'b'? *sigh*
That was true for 1.3, for 1.4 the format is different, and it uses the
letters. See development/FORMAT.
> Andre'
--
Jos� Ab�lio
LyX and docbook, a perfect match. :-)
