SPEX / Dept. of Language and Speech University of Nijmegen Erasmusplein 1 NL-6525 HT Nijmegen The Netherlands SUBJECT: Validation Finnish FDB SpeechDat corpus AUTHORS: Henk van den Heuvel, Eric Sanders VERSION: 1.0 DATE : 1 December 1998 The speech databases made within the SpeechDat project were validated by SPEX, Leidschendam, the Netherlands, to assess their compliance with the SpeechDat format and content specifications, as documented in Deliverables 1.3.1, 1.3.2 and 1.3.3 of the project. The validation results of the Finnish Fixed Network SpeechDat database (4000 speakers) are contained in this document. This database was validated and approved by the SpeechDat Consortium. In the validation procedure we systematically check a list of validation criteria for a range of subjects. In the following sections we will evaluate these criteria one by one. Validation results that call for attention because of deviations from the SpeechDat specifications are marked by =>. They can be easily extracted/'grepped' in this way. The following subjects were validated: 1 DOCUMENTATION 2 DATABASE STRUCTURE, CONTENTS AND FILE NAMES 3 ITEMS 4 SAMPLED DATA FILES 5 ANNOTATION FILES 6 LEXICON 7 SPEAKERS 8 RECORDING PLATFORM 9 TRANSCRIPTION The document is concluded by 10 SUMMARY ==================================================================== 1. DOCUMENTATION - File DESIGN.DOC; & deliverables SD131 and SD132 can be handy File DESIGN.DOC is present - Language of doc file: English OK - Contact person: name, address, affiliation OK, cover page - Number of CDs OK, section 1 - Contents of each CD OK, section 1 - The directory structure of the CDs OK, sections 1 and 1.3 - Description of all the items in the corpus OK, section 1.2 and 3. But the following remarks need to be made: => . How is the sheet number in section 3.3.1 composed? => . The number of different credit card numbers (3.3.3) and => PIN-codes (3.3.4) should be given (150 each) => . The list of credit card numbers could be added; it is inconsistent => to have only the list of PIN-codes => . In section 3.4.2 we recommend to list the different week day, => and month names together with a translation into English => . In section 3.11 information is missing as to how many => different sentences were used in the prompts => . In section 3.13 information is missing as to how many => different words were used in the prompts - Prompting . linguistic specification (and motivation) for the prompting material (in case of additional optional items) . connection of sheet items to item numbers on CD . sheet example . items must be spread over the sheet to prevent list effects (e.g. three yes/no questions immediately after another are not allowed) OK, sections 1.2, 2.3 and 8 - Naming conventions for directories and files OK, sections 1.2 and 1.3 - Speaker recruitment OK, section 2.2 - Speaker demographics . which regions, how many of each . motivation for selection of regions . which age groups, how many of each . sexes: males, females, also children?; how many of each. . each call is made by a unique speaker OK, section 4 - Analysis of frequency of occurrence of the sub-word units represented in the phonetically rich sentences (either of phones, biphones, triphones) OK, section 3.11 - Analysis of frequency of occurrence of the sub-word units represented in the phonetically rich words (either of phones, biphones, triphones) OK, section 3.13 - Recording platform and telephone link description OK, section 2.1 - Signal characteristics (number of bits per sample; bandwidth; coding type; compression procedures) OK, section 1.1 - The format of the speech files (A-law, 8 bit, 8 kHz, uncompressed) OK, section 1.1 - The format of the annotation files (SAM label files) OK, section 1.4 - Annotation . procedure . quality assurance . character set used for annotation (transcription) (ISO-8859) . annotations symbols for non-speech acoustic events must be mentioned at least for Filled Pause, Speaker Noise, Stationary Noise, Intermittent Noise. . list of symbols used to denote word truncations, mispronunciations and not understandable speech . case sensitivity of transcriptions OK, section 2.4 => A reference to TRANSCRP.DOC is missing. - Lexicon information . Procedures to obtain phonemic forms from orthographic input (lexicon generation and lay out) . (Reference to) SAMPA symbols used . case sensitivity of entries (matching the transcriptions) OK, section 5 - Only one spelling of each word is allowed. Therefore a list of normalised spellings for words with alternative spellings should be included (SPELLALT.DOC). Otherwise a statement why such a list is not necessary. OK, section 2,4 - Indication of how many of the files were double checked by the producer together with percentage of detected errors OK, section 5 - The validation report made by SPEX (VALREP.TXT) is referred to OK - Other remarks: => Section 1 needs update after validation ========================================================================== 2. DATABASE STRUCTURE CONTENTS AND FILE NAMES - Directory / subdirectory conventions Format of directory tree should be \\\ . data base: defined as <#> can be FIXED, MOBIL, VERIF <#> is 0 for SpeechDat(M) and 1 for SpeechDat is the ISO two-letter code for the language . block : defined as BLOCK where is a progressive number from 00 to 99. Block numbers are unique over all CDs. They correspond to the first two digits of below. . session: defined as SES where is the session code also appearing in file name OK - All text files should be in MS-DOS format () at line ends => All label files in SES3428 contain not readable code - A README.TXT file should be in the root describing all (documentation) files on the CD-ROM. OK - A file containing a shortened version of the volume name (11 chars max.) should be in the root directory. The name of this file is DISK.ID. This file supplies the volume label to UNIX systems that cannot read the physical volume label. Example of contents: FIXED1EN_01. OK - A copyright statement should be present in the file COPYRIGH.TXT (root) OK - Documentation should be in \\DOC . DESIGN.DOC . TRANSCRP.DOC (optional) . SPELLALT.DOC (optional) . SAMPALEX.PS . ISO8859<1,2,7>.PS . SUMMARY.TXT . SAMPSTAT.TXT OK, including the optional TRANSCRP.DOC - The contents list (CONTENTS.LST) is in \\INDEX OK - Tables should be in \\TABLE . SPEAKER.TBL . LEXICON.TBL . REC_COND.TBL (optional) . SESSION.TBL (optional) OK, including SESSION.TBL - Index files (optional) should be in \\INDEX OK - The index files (if present) obey the nomenclature .LST where e.g. A1ENN3.LST (see below for item_code) Not provided - Prompt sheet files (optional) should be in \\PROMPT Not provided - All sessions indicated in the documentation SUMMARY.TXT are present on the CDs OK - File naming conventions All file names should obey the following pattern: DDNNNNCC.LLF DD : database identification code For SpeechDat : A1 = fixed net, B1 = mobile, C1 = speaker verification NNNN : session code 0000 to 9999 CC : item code; first character is item type identifier, second character is item number LL : ISO-639 language code (with extensions) F : speech file type A is for A-law O is for Orthographic label file OK - Correct item codes should be used: A1-3/6: common application words B1 : sequence of isolated digits C1 : prompt sheet number C2 : telephone number C3 : credit card number C4 : PIN code D1-3 : dates E1 : application word phrase I1 : isolated digit L1-3 : spelled words M1 : money amount N1 : natural number O1 : spontaneous name O2 : city of call/birth O3 : most frequent city name O5 : most frequent company/agency name O7 : forename & surname Q1-2 : yes/no questions S1-9 : phonetically rich sentences T1 : time of day T2 : time phrase W1-4 : phonetically rich words OK, see also section 3 - NNNN in filenames is not in conflict with BLOCK and SES numbers in pathname OK - Contents lowest level subdirectories should be of one call only OK - Empty (i.e. zero-length) files are not permitted => The file A12757D1.FIO is empty - Missing items per speaker Check with documentation (SUMMARY.TXT) OK - File match: For each label file there must be one speech file and vice versa. => For file A13485O1.FIO there is no matchin speech file - Part of the corpus is designed for training and a smaller part for testing. OK There is one file with test sessions: \FIXED1FI\INDEX\A1TSTFI.SES It contains 500 sessions from existing calls. - All table files, and index files should report the field names as the first row in the files using tabs as in the data records following. OK - The contents of the database as given in CONTENTS.LST should comprise . CD-ROM volume name (VOL:) . full pathname (DIR:) . speech file name (SRC:) . corpus code (CCD:) . corpus repetition (CRP:) . speaker code (SCD:) . speaker sex (SEX:) . speaker age (AGE:) . speaker accent (ACC:) . orthographic transcription of uttered item (LBO:) The first line should be a header specifying the information in each record. This file must be supplied as an ASCII TAB delimited file. OK - The contents of the SUMMARY.TXT files should comprise: . The full directory name where speech and label files are to be found . the session number . a string of typically N codes. Each item present is represented by its code. If the item is missing, a '--' should appear. . recording date . recording time of first item . optional comment text . all these fields are separated by spaces . Note: The contents of the SUMMARY.TXT file are not CD-dependent OK ====================================================================== 3. ITEMS - 1 isolated digit (code I1) . read or prompted OK - 1 sequence of 10 isolated digit (code B1) . each sequence must include all digits . optional are hash and star OK - 4 connected digits (code C1-4) - 4-6 digit number to identify the prompt sheet . read - ~10 digit telephone number . read . local numbers . inclusion of GSM numbers recommended - 14-16 digit credit card number . read . set of 150 . if there is a checksum then formula must be provided - 6 digit PIN code . read . set of 150 . ~30 digits per call are required . digits must appear numerically on the sheet, not as words OK, all these items are recorded, yielding 37 digits per call. We observed 150 different credit card numbers in good distribution; we observed 150 different PIN-codes in good distribution; In both C3 and C4 we found one occurrence of the word "kokemuksesta" - 1 natural number (code N1) . read . provided as numbers (numerically) . numbers must be < 1,000,000 . decimal numbers only allowed for additional natural numbers OK - 1 money amount (code M1) . read . currency words should be included . mixture of small amount including decimals and large amounts not including decimals OK - 3 spelled words (code L1-3) . L1 is spontaneous name spelling linked to O1 . others are read . equal balance of all vocabulary letters artificial words can be used to enforce this balance . average length at least 7 letters . may include names, cities and other frequently spelled items . should include equivalents of : A-Z, accent words, CAPITAL, SMALL, UPPER-CASE, LOWER-CASE, DOUBLE, APOSTROPHE, HYPHEN OK, but equivalents of CAPITAL, SMALL, UPPER-CASE, LOWER-CASE, DOUBLE, APOSTROPHE, HYPHEN are not included in the prompting material. - 1 time of day (code T1) . spontaneous OK - 1 time phrase (code T2) . read . analogue form . equal balance of all words . should include equivalents of : AM/PM, HALF/QUARTER PAST/TO, NOON, MIDNIGHT, MORNING, AFTERNOON, EVENING, NIGHT, TODAY, YESTERDAY, TOMORROW OK - 1 date (code D1) . spontaneous OK - 1 date (code D2) . read, wordstyle . analogue form . covering all weekdays and months, ordinals and year expressions (also exceeding 2000) OK, years exceeding 2000 were not prompted - 1 relative date (code D3) . read . analogue . should include forms such as TODAY, TOMORROW, THE DAY AFTER TOMORROW, THE NEXT DAY, THE DAY AFTER THAT, NEXT WEEK, GOOD FRIDAY, EASTER MONDAY, etc. OK, each expression appears at least 50 times - 2 yes/no questions (code Q1-2) . spontaneous, not prompted . one question should elicit (predominantly) 'no' answers; the other (predominantly) 'yes' answers . also fuzzy answers should be envisaged OK - 3/6 common application words (code A1-3/6) . read . set of 30 should be used, 25 of which are fixed for all . minimum number of examples of each word = #speakers/10 (this is a soft target) . 6 are needed, but only 3 for 4000+ FDBs OK, 3 application words per call were recorded 30 different words were recorded (see section 3.1 of DESIGN.DOC); each word appears about 400 times but at least 350 times. The word "kokemuksesta" appears 3 times and is an erroneous word - 1 application word phrase (code E1) . application word is embedded in phrase . read or spontaneous OK - 9 phonetically rich sentences (code S1-9) . read . minimum number of phone examples = #speakers/10 OK, less than 400 realisations for a phone are only observed for the phones of foreign origin. - 4 phonetically rich words (code W1-4) . read . minimum number of phone examples = #speakers/5 OK Of the more common phones the following have less than 800 samples: /22,kk,mm,N,NN,oo,pp,rr,yy/. Of these some have even less than 400 samples: /22, NN, oo, pp, rr, yy/, being: 343, 71, 164, 159, 73, 263 respectively Since the latter phones are geminates which hardly differ from their corresponding monophones in acoustic terms (apart from duration), merging is well possible. In this case only /N/ remains with less than 800 samples (viz. 427) - 5 directory assistance names (code O1-7) . 1 spontaneous name (e.g. forename) . 1 spontaneous city name . 1 read city name (from list of 500 most frequent) . 1 read company/agency name (from list of 500 most frequent) . 1 read proper name, fore- and surname (from list of 150 SDB names) OK A list of 223 city names, instead of 500, was used, but this is explained in section 3.9.3 of DESIGN.DOC Only 490 of the 500 company names were used => In each item the illegal "kokemuksesta" shows up The following completeness checks are performed on obligatory SpeechDat items only: 1. Structurally missing items There are no structurally missing items. (And there are no optional additional items either) 2. Incidentally missing items a. files that are not there 47 files were found missing, according to the following distribution over the corpus codes: A3: 1 B1: 3 C2: 1 C3: 1 C4: 3 D2: 2 D3: 2 E1: 1 I1: 2 L1: 1 L3: 1 M1: 1 N1: 2 O5: 1 O7: 1 S3: 3 S4: 2 S5: 1 S6: 1 S7: 2 S8: 3 S9: 5 W1: 1 W2: 1 W3: 2 W4: 3 Furthermore there was one empty label file with corpus code D1. b. files with empty transcriptions in the LBO label field (effectively missing files) We found 274 files that have only noise symbols and/or ** in their transcriptions. If we merge these the empty and missing files, we get the following distribution over the corpus codes: 8 A1 10 A2 6 A3 4 B1 2 C1 5 C2 5 C3 6 C4 6 D1 5 D2 8 D3 1 E1 7 I1 7 L1 5 L2 7 L3 1 M1 4 N1 18 O1 32 O2 5 O3 3 O5 3 O7 51 Q1 22 Q2 4 S1 5 S2 6 S3 3 S4 4 S5 5 S6 6 S7 7 S8 6 S9 30 T1 5 T2 6 W1 7 W2 6 W3 11 W4 c. corrupted speech files If we regard utterances which have only truncated or mispronounced words as corrupted files, and merge these with the effectively missing files under b. then the following distribution emerges : 15 A1 22 A2 15 A3 4 B1 2 C1 5 C2 5 C3 6 C4 6 D1 5 D2 12 D3 2 E1 15 I1 8 L1 5 L2 7 L3 1 M1 4 N1 23 O1 35 O2 22 O3 5 O5 5 O7 58 Q1 23 Q2 4 S1 5 S2 6 S3 3 S4 4 S5 6 S6 6 S7 9 S8 6 S9 30 T1 6 T2 26 W1 26 W2 26 W3 24 W4 (This will not be used to reject or approve a database but it will be supplied as supplementary information.) d. files containing truncation and mispronunciation marks (*,**,~ are counted in the transcriptions of the individual items to get an idea of distorted speech data. This will not be used to reject or approve a database but it will be supplied as supplementary information.) We found 6140 transcriptions with at least one *, or **, or ~, according to the following distribution over the items: A1: 36 A2: 44 A3: 36 B1: 85 C1: 54 C2: 83 C3: 166 C4: 58 D1: 238 D2: 234 D3: 45 E1: 58 I1: 34 L1: 139 L2: 150 L3: 260 M1: 169 N1: 113 O1: 75 O2: 73 O3: 80 O5: 150 O7: 76 Q1: 61 Q2: 38 S1: 322 S2: 301 S3: 345 S4: 358 S5: 368 S6: 378 S7: 369 S8: 365 S9: 379 T1: 104 T2: 53 W1: 66 W2: 81 W3: 49 W4: 47 3. Overall conclusion SpeechDat has the following criteria for missing items: . At least 95% of the files of each mandatory item (corpus code) must be present. . As missing files are counted: absent files, and files containing non-speech events only. . There will be no further comparison of prompt and transcription text in order to decide if a file is effectively missing. As a consequence: If there is some speech in the transcription, then the file will NOT be considered missing, even if it is in fact useless. For a database of 4000 calls a maximum of 5% * 4000 = 200 files per item may be missing. For the decision of completeness of an item the distribution given in 2b above should be used. It is clear from this distribution that none of the items effectively misses 200 or more files. This even holds if the corrupted speech utterances are included. =========================================================================== 4. SAMPLED DATA FILES 1 Coding . A-law, 8 bit, 8 kHz, no compression OK 2 Sample distribution Several sample statistics are generated: File length, clipping rate, mean sample value, Signal-to-Noise Ratio (SNR). Statistics were generated on file level by the producer of the database, using SPEX software. The results were delivered to SPEX. SPEX compiled histograms on the basis these results. These histograms are presented below, both on file level and on directory (call) level. The histograms are presented as they are and not further interpreted by SPEX. On the basis of these data the user of the database should be able to decide which acoustic quality is still acceptable for the application at hand. Statistics on the acoustics of individual speech files can be retrieved from file \DOC\SAMPSTAT.TXT. The columns in SAMPSTAT.TXT have the following meaning: file max min #samples cliprate mean snr A11001C2.ENA:16384:-13056:80000: 0.00: -4.28: 35.89 2.1 File length We calculated the length of the files in seconds in order to trace spurious recordings if files were of extraordinary length. Duration distribution over all items: Length (s) #Occurrences 1 - 2 : 22 2 - 3 : 21942 3 - 4 : 33839 4 - 5 : 23627 5 - 6 : 26244 6 - 7 : 19636 7 - 8 : 18761 8 - 9 : 5610 9 - 10 : 3698 10 - 11 : 2232 11 - 12 : 1413 12 - 13 : 2928 Duration distribution over calls/directories: Length (s) #Occurrences 3 - 4 : 13 4 - 5 : 1351 5 - 6 : 2077 6 - 7 : 470 7 - 8 : 81 8 - 9 : 8 2.2 min-max samples We provide a histogram with clipping ratios, The clipping ratio is defined as the proportion of samples in a file that is equal to the maximum/minimum value, divided by all samples in the file. The histogram, then, is an overview of how many files were found in a set of clipping rate intervals. Clip distribution for all items: Clipping Occurrences rate (in %) 0.0 - 0.1 : 6548 0.1 - 0.2 : 892 0.2 - 0.3 : 338 0.3 - 0.4 : 151 0.4 - 0.5 : 97 0.5 - 0.6 : 68 0.6 - 0.7 : 38 0.7 - 0.8 : 23 0.8 - 0.9 : 9 0.9 - 1.0 : 13 1.0 - 1.1 : 13 1.1 - 1.2 : 7 1.2 - 1.3 : 2 1.3 - 1.4 : 8 1.4 - 1.5 : 10 1.5 - 1.6 : 2 1.6 - 1.7 : 2 1.7 - 1.8 : 1 2.0 - 2.1 : 1 2.1 - 2.2 : 2 2.2 - 2.3 : 1 2.5 - 2.6 : 1 2.6 - 2.7 : 1 2.9 - 3.0 : 1 3.2 - 3.3 : 1 4.4 - 4.5 : 1 4.9 - 5.0 : 1 5.7 - 5.8 : 1 6.0 - 6.1 : 2 Number of files with absolute maximum < 32256: 151717 Clip distribution over calls/directories: Clipping Occurrences rate (in %) 0.0 - 0.1 : 1016 0.1 - 0.2 : 29 0.2 - 0.3 : 6 0.3 - 0.4 : 5 0.4 - 0.5 : 1 1.3 - 1.4 : 1 => There is one call with an average clipping rate more than 1.0%: SES3284 => This call is severly clipped and contains a lot of not-serious speech 2.3 Mean values We computed the mean sample value of each item in each call. We provide a histogram with mean values below. The histogram, then, is an overview of how many files were found in a set of mean sample value intervals. This overview can be used to trace files with large DC-offsets. Mean distribution over all items: Mean Occurrences -200 - -190 : 1 -140 - -130 : 2 -130 - -120 : 3 -120 - -110 : 65 -110 - -100 : 34 -100 - -90 : 70 -90 - -80 : 154 -80 - -70 : 298 -70 - -60 : 601 -60 - -50 : 762 -50 - -40 : 1065 -40 - -30 : 1915 -30 - -20 : 3985 -20 - -10 : 16410 -10 - 0 : 46370 0 - 10 : 79789 10 - 20 : 7217 20 - 30 : 731 30 - 40 : 241 40 - 50 : 157 50 - 60 : 19 60 - 70 : 47 70 - 80 : 4 80 - 90 : 9 90 - 100 : 1 140 - 150 : 1 260 - 270 : 1 Mean distribution over calls/directories: Mean Occurrences -120 - -110 : 2 -90 - -80 : 3 -80 - -70 : 7 -70 - -60 : 9 -60 - -50 : 20 -50 - -40 : 26 -40 - -30 : 44 -30 - -20 : 101 -20 - -10 : 459 -10 - 0 : 1137 0 - 10 : 2004 10 - 20 : 165 20 - 30 : 14 30 - 40 : 4 40 - 50 : 4 60 - 70 : 1 2.4 Signal to Noise Ratio We split each signal file into contiguous windows of 10 ms and computed the Mean Square (energy) in each window. The mean sample value over the complete file was subtracted from each individual sample value before MS was computed. 5% of the windows that contained the lowest energy were assumed to contain line noise. In this way the signal to noise ratio could be calculated for each file by dividing the mean energy over all windows by the mean energy of the 5% sample mentioned above. The result was multiplied by 10*log for scaling. SNR distribution over all items: SNR occurrences 5 - 10 : 35 10 - 15 : 171 15 - 20 : 736 20 - 25 : 3637 25 - 30 : 13794 30 - 35 : 30672 35 - 40 : 42250 40 - 45 : 36197 45 - 50 : 20486 50 - 55 : 7586 55 - 60 : 2276 60 - 65 : 1028 65 - 70 : 495 70 - 75 : 281 75 - 80 : 136 80 - 85 : 84 85 - 90 : 51 90 - 95 : 17 95 - 100 : 8 100 - 105 : 7 105 - 110 : 2 110 - 115 : 2 125 - 130 : 1 SNR distribution over calls/directories: SNR occurrences 10 - 15 : 2 15 - 20 : 11 20 - 25 : 58 25 - 30 : 296 30 - 35 : 741 35 - 40 : 1201 40 - 45 : 943 45 - 50 : 515 50 - 55 : 170 55 - 60 : 47 60 - 65 : 10 65 - 70 : 5 70 - 75 : 1 There are no calls with an average SNR below 10 dB =========================================================================== 5. ANNOTATION FILE - Each line must be delimited by OK, => apart from the label files in session 3428 DOS-formatted files are provided - Mandatory (SAM) mnemonics: LHD: SAM, 5.10 DBN: SPEECHDAT__Fixed_Network VOL: FIXED1_ SES: DIR: SRC: CCD: CRP: < = corpus repetition, empty> REP: RED: RET: SAM: 8000 < = sampling freq.> BEG: END: SNB: 1 < = number of bytes per sample> SBF: < = sample byte order, meaningless with single bytes> SSB: 8 < = number of significant bits per sample> QNT: A-LAW < = quantisation> SCD: SEX: M/F/UNKNOWN AGE: ! mnemo is not SAM ACC: ! mnemo is not SAM REG: ENV: LBD: LBR: , , [gain], [minimum value], [maximum value], LBO: , [centre sample], , EXT: 80 chars on one line> ELF: - Optional (SAM) mnemonics (may be omitted or left empty) TYP: orthographic TXF: CMT: NCH: 1 < = number of channels recorded> ARC: ! mnemo is not SAM SHT: ! mnemo is not SAM CMP: EXP: SYS: DAT: SPA: PHM: ! mnemo is not SAM NET: PSTN < = network> ! mnemo is not SAM DSC: < = discontinuity marker> EDU: ! mnemo is not SAM SOC: ! mnemo is not SAM HLT: TRD: RCC: ASS: ! mnemo is not SAM - Order restrictions: . LHD and TYP are first . LBR and LBO come after LBD . ELF is end of file keyword => Some errors were found in the order of mnemonics: => A11462S5.FIO: EXT after ELF; due to two ELF mnemonics in file => A12502S9.FIO: EXT after ELF; due to two ELF mnemonics in file => A12829S2.FIO: EXT after ELF; due to two ELF mnemonics in file - All mnemonics should be SAM mnemonics or explicitly defined in documentation OK - No illegal mnemonics used => A few incidental errors in the mnemonics were found: => A10506T1.FIO: 'LHD instead of LHD => A12814M1.FIO: 'LHD instead of LHD - There are no mnemonics missing OK - All files must contain the same mnemonics. This holds as well for the optional mnemonics. OK - No illegal field values should appear => Label files in SES2832 and 3385 have wrong values for the SEX mnemonic. They have "Mm" instead of "M" => Sessions 1426, 2210, 3805 show multiple age values in the label files => File A11491O1.FIO has a value for ACC which differs from the other => label files in the session => File A13550O1.FIO has a value for ACC which differs from the other => label files in the session => The following illegal values were LBR were observed: => A10068B1.FIO: 1653Suurempia hankaluuksia ei tullissa ole ollut => A13276B1.FIO: 82594037Hatanpään päivystysasemalla näkyy taudin koko kuva => A13723B1.FIO: 81764Niinpä kölniläiset kansoittivat rangaistuspenkkiä alinomaa - No line may exceed 80 chars => We observed 9 label files with too long lines: => A10370S9.FIO: LBO: 81 => A10404S8.FIO: LBO: 81 => A10496S3.FIO: EXT: 81 => A10501S2.FIO: LBO: 81 => A11366S4.FIO: LBO: 81 => A11686D2.FIO: LBO: 81 => A11765S9.FIO: LBO: 81 => A12044E1.FIO: LBO: 82 => A13379S6.FIO: LBO: 81 - Each lowest subdirectory does not refer to multiple sheet ids. OK - For spontaneous speech LBR should contain a mnemonic word. D1 : L1 : O1 : O2 : Q1 : or Q2 : or T1 :