While writing this post, I just thought: why Regex? So I came up with another solution, not elegant, but it seems to work just fine.

use strict;
use warnings;

require Text::Extract::Word;
Text::Extract::Word->import( qw(get_all_text) );

my $InputFileReadable ='Input.doc';
my $content = get_all_text($InputFileReadable);
#detecting structure
my ($header, $body)= split /(\a)\1+/, $content;
my $NrSeparators = () = $header =~ /\a/g;

my @cells = split(/\a/, $content);
my $count=0;

open(FH, '>', "Output.txt") or die $!;
foreach (@cells){
    $count++;
    print FH $_;
    if ($count eq $NrSeparators+2){
        print  FH "\n";
    }else{
        print  FH "\t";
    }
    $count = 0 if $count eq $NrSeparators+2;
}
close(FH);

[download]

In reply to Re: parsing table .doc by IB2017
in thread parsing table .doc by IB2017

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.