[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: consultants/ won't build



On Wed, Dec 05, 2001 at 09:47:08AM -0500, James A. Treacy wrote:
> On Wed, Dec 05, 2001 at 02:23:36PM +0100, Denis Barbier wrote:
> > > 
> > > wml -q -D CUR_YEAR=2001 -o UNDEFuEN:index.en.html@g+w   index.wml
> > > ePerl:Error: Cannot convert bristled code file `/tmp/wml.31971.tmp1.wml' to pure HTML
> > > ** WML:Break: Error in Pass 3 (rc=74).
> > > make: *** [index.en.html] Error 1
> > > 
> > > whatever the hell that means...
> > 
> > Broken consultant.data, a patch is attached (I cannot commit from my box here).
> > 
> [snip]
> > -<phone   +359-2-9877088
> > +<phone   +359-2-9877088>
> 
> Do you have an easy way of tracking down this sort of thing?

Yes, run mp4h alone through input files.
I will check why in this case number line is wrong, but it is anyway
very easy to find where it fails since processing stops at the wrong line.

> Also, slices that aren't closed are a pain to find.

The problem is that slices do not have to be properly nested (and this
cannot be changed, some applications do rely on this), so trapping errors
are indeed difficult.
There are 2 solutions:
  a) use explicit name at end of slices, e.g. [EN:...:EN] to help `slice'
     write accurate reports
  b) define tags to ensure proper nesting, e.g. <en>...</en> which will
     be expanded into [EN:...:EN] during pass 2.
     This example is wrong, since hr, br and others would cause trouble,
     you will have to use a proper namespace.
I would much appreciate if any of these solutions is adopted, it would
help me to improve the define-tag-sliced tag in 2 ways:
  * support for nested slices due to variants (e.g. Chinese)
  * allow multiline text

> It would be really cool if wml gave a line number and a file name (the
> problem may be in an included file) when it pukes.

Yes, I tried, but it is a pain because passes are independent.
This example gives me an idea for this specific case, but I fear there is
no general solution for this issue.
Of course, all improvements are welcome.

Denis



Reply to: