Hi Ales,
Yes, you found the problem. I noticed that using the newline.sym as it
was caused libgeda to fail handling the newline character, so I prefered
to leave things as they were.
Long time ago, I didn't find any problem because of the missing break
statement.
I didn't know that libgeda wasn't loading the newline character if it
didn't contain anything. Thanks for explaining the libgeda behaviour!
Carlos
El dom, 06-03-2005 a las 16:11 -0500, Ales Hvezda escribi�:
> Hi Carlos again,
>
> [snip]
> >o_text_set_info_font: character ! not found!!!
> >
> >
> >Okay, but why? I noticed in system-gafrc.in:
> >
> >; The newline.sym symbol is not used!!. Use excl.sym or the newline
> >; will not be handled correctly!!.
> >
> >Why isn't newline.sym being used and what causes this breakage?
> >
>
> After looking at the code, I understand now. newline.sym is
> a rather empty font def file, so the statements inside the following if
> statement (o_text_basic.nw:744) never got executed if newline.sym was
> loaded into the hash table:
>
> ...
> if (o_font_set->font_prim_objs->next != NULL) {
> ...
>
> However, if I put an object (line etc...; can be anything since it is
> ignored) into newline.sym then multi-line text lines work again.
>
> I have checked the necessary changes into CVS. Please let me know if
> you think this fixes the problem sufficiently.
>
> -Ales
>
--
Carlos Nieves �nega <[EMAIL PROTECTED]>
---Publicidad--------------------------------------------------------
Melod�as y Juegos flipantes para tu m�vil � Desc�rgalas !
http://www.mobileparty.net/?loginw8336
