Problem:

I have various files named *.language which contain hashes like: $LANGUAGE{content_index_misc_this} = qq~blah~; I need to convert any such items to $LANGUAGE{CONTENT_INDEX}{MISC}{THIS} = qq~blah~; The CONTENT_INDEX part is parsed from the filename, eg content_index.language. The rest needs to be converted to upper case and '_' switched for '}{'. The files are not structured, the hashes could be anywhere with none or many on each line.

I have been given this code (thanks), however, it presumes there is only two hashes to create after the content_index (misc, this) and there could be several. Also, the content_index part will change depending on the file being parsed.

#!c:\perl\bin\perl.exe $c="\$LANGUAGE{content_index_misc_this} = qq~blah~;"; $c =~ s/(\{)(.+)(\})/$1\ U$2\E$3/g; $c =~ s/_/\}\{/g; $c =~ s/(content)\}\{( index)/$1_$2/i; print $c, "\n";'

In reply to Perl Parsing Pedantics by snoopyac

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.