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

Bug#712026: RFS: transcriber/1.5.1.1-7 [RC] -- Transcribe speech data using an integrated editor

Hi,

Am Wed, 12 Jun 2013 17:52:03 +0300
schrieb Sergei Golovan <sgolovan@nes.ru>:

> Apparently, tcLex doesn't work with Tcl 8.5. I'll look into it in a
> few days.
> 
> Cheers!
> -- 
> Sergei Golovan

tcLex is currently not working with tcl8.5, but with tcl8.4.

The url specified in the help message does not work for me:
http://www.etca.fr/CTA/gip/Projets/Transcriber/

Please add the possibility to specifiy an output directory.
It would be nice to handle, if no argument is given.
How can i transcribe wav to html? I found no hint for this.

< file:///home/kardan/build/transcriber/doc/Index.html
> When Transcriber is correctly installed, it can be started with the
> command: trans

$ ./trans
can't read "v(wavfm,list)": no such element in array
    while executing
"foreach wavfm $v(wavfm,list) {
      ConfigWavfm $wavfm $mode
   }"
    (procedure "ConfigAllWavfm" line 4)
    invoked from within
"ConfigAllWavfm $mode"
    (procedure "EmptySignal" line 35)
    invoked from within
"EmptySignal"
    (procedure "StartWith" line 270)
    invoked from within
"StartWith $argv"
    (procedure "Main" line 16)
    invoked from within
"Main $argv"
    (file "../tcl/Main.tcl" line 1115)

A more descriptive message could help to user who is inputting
nonsense.

$ ./trans ../demo/frint980428.wav 
can't read "v(wavfm,list)": no such element in array
    while executing
"foreach wavfm $v(wavfm,list) {
      ConfigWavfm $wavfm $mode
   }"
    (procedure "ConfigAllWavfm" line 4)
    invoked from within
"ConfigAllWavfm $mode"
    (procedure "EmptySignal" line 35)
    invoked from within
"EmptySignal"
    (procedure "StartWith" line 270)
    invoked from within
"StartWith $argv"
    (procedure "Main" line 16)
    invoked from within
"Main $argv"
    (file "../tcl/Main.tcl" line 1115)

$ ./trans -export lbl ../demo/frint980428.trs                                        
Converting transcription files to lbl format (.lbl):
converting ../demo/frint980428.trs (trs)
error with ../demo/frint980428.trs: can't read "v(trans,seg0)": no such element in array (can't read "v(trans,seg0)": no such
 element in array
    while executing
"foreach s $v(trans,seg0) {
       foreach {t0 t1 text} $s break
       set t0 [Synchro::GetTime $t0]
       set t1 [Synchro::GetTime $t1]
       if {$..."
    (procedure "::convert::lbl::export" line 5)
    invoked from within
"${nsformat}::export [file tail [file root $name]]$ext")
0 file(s) processed.

$ ./trans -export
cha ../demo/frint980428.trs Converting transcription files to cha
format (.cha): converting ../demo/frint980428.trs (trs)
error with ../demo/frint980428.trs: Attribute 'role' for type 'Speaker'
not defined in DTD (Attribute 'role' for type 'Speake r' not defined in
DTD while executing
"error "Attribute '$name' for type '$type' not defined in DTD""
    (procedure "::xml::dtd::attribute::default" line 6)
    invoked from within
"${xml}::dtd::attribute::default [$item getType] $attr 1"
    (procedure "::xml::element::getAttr" line 10)
    invoked from within
"::xml::element::getAttr ::xml::element4 role"
    ("eval" body line 1)
    invoked from within
"eval $cmd $item $lst_args"
    (procedure "::xml::CheckEval" line 19)
    invoked from within
"::xml::CheckEval element $method ::xml::element4 $args"
    (procedure "::xml::element4" line 1)
    invoked from within
"$speaker getAttr "role"
    (procedure "::convert::cha::export" line 23)
    invoked from within
"${nsformat}::export [file tail [file root $name]]$ext")
0 file(s) processed.

The html output looks good except the header (find the html errors
attached). A nice tool though.

Hope this is productive,
kardan
Title: [Invalid] Markup Validation of frint980428.html - W3C Markup Validator

Errors found while checking this document as HTML 4.01 Transitional!

Result: 6 Errors, 5 warning(s)
:

Use the file selection box above if you wish to re-validate the uploaded file frint980428.html
: windows-1252 (detect automatically) utf-8 (Unicode, worldwide) utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2 (Central Europe) iso-8859-3 (Southern Europe) iso-8859-4 (North European) iso-8859-5 (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8 (Hebrew, visual) iso-8859-8-i (Hebrew, logical) iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-11 (Latin/Thai) iso-8859-13 (Latin 7, Baltic Rim) iso-8859-14 (Latin 8, Celtic) iso-8859-15 (Latin 9) iso-8859-16 (Latin 10) us-ascii (basic English) euc-jp (Japanese, Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email) euc-kr (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified) big5 (Chinese, traditional) Big5-HKSCS (Chinese, Hong Kong) tis-620 (Thai) koi8-r (Russian) koi8-u (Ukrainian) iso-ir-111 (Cyrillic KOI-8) macintosh (MacRoman) windows-1250 (Central Europe) windows-1251 (Cyrillic) windows-1252 (Western Europe) windows-1253 (Greek) windows-1254 (Turkish) windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim)
: HTML 4.01 Transitional (detect automatically) HTML5 (experimental) XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01 Frameset HTML 4.01 + RDFa 1.1 HTML 3.2 HTML 2.0 ISO/IEC 15445:2000 ("ISO HTML") XHTML 1.1 XHTML + RDFa XHTML Basic 1.0 XHTML Basic 1.1 XHTML Mobile Profile 1.2 XHTML-Print 1.0 XHTML 1.1 plus MathML 2.0 XHTML 1.1 plus MathML 2.0 plus SVG 1.1 MathML 2.0 SVG 1.0 SVG 1.1 SVG 1.1 Tiny SVG 1.1 Basic SMIL 1.0 SMIL 2.0
Root Element: html
Options

Help on the options is available.

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

  1. Warning No Character Encoding Found! Falling back to windows-1252.

    None of the standards sources gave any information on the character encoding labeling for this document. Without encoding information it is impossible to reliably validate the document. As a fallback solution, the "windows-1252" encoding was used to read the content and attempt to perform the validation, but this is likely to fail for all non-trivial documents.

    Before defaulting to windows-1252 the validator also tried to read the content with the following encoding(s), without success: UTF-8.

    Read the FAQ entry on character encoding for more details and pointers on how to fix this problem with your document.

  2. Warning Unable to Determine Parse Mode!

    The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:

    • the MIME Media Type (text/html) can be used for XML or SGML document types
    • No known Document Type could be detected
    • No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
    • No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.

    As a default, the validator is falling back to SGML mode.

  3. Warning No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.

    No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.

    The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.

    Learn how to add a doctype to your document from our FAQ.

  4. Info No Character encoding declared at document level

    No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.

    See this tutorial on character encoding for techniques and explanations.

↑ Top

Validation Output: 6 Errors

  1. Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>" 
    <html>

    ✉

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  2. Error Line 8, Column 12: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag 
    <h1><center></center></h1>

    ✉

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    p> One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  3. Error Line 15, Column 12: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag 
    <h2><center><font color="#990000">filler</font></center></h2>

    ✉

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  4. Error Line 42, Column 12: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag 
    <h2><center><font color="#990000">nontrans</font></center></h2>

    ✉

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  5. Error Line 50, Column 12: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag 
    <h2><center><font color="#990000">filler</font></center></h2>

    ✉

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  6. Error Line 57, Column 12: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag 
    <h2><center><font color="#990000">report - les titres</font></center></h2>

    ✉

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

↑ Top

Reply to: