Menu

Latest release 2.6

Help
Anonymous
2020-04-17
2020-04-18
  • Anonymous

    Anonymous - 2020-04-17

    Hi:
    With your latest release everything just works fine EXCEPT I have not been able to get my html results in a box with borders the way it always came out before! Last 3-4 years I generate my output via the command line on windows & I hate to tell anyone publicly but I just dumped your files into my XAMPP perl bin & never have a problem. So I have included an example. As I have said before your software is a great contribution.
    Thanks

    Phil

     
  • metaf2xml

    metaf2xml - 2020-04-17

    Hi Phil,

    thanks a lot for the praise, and sorry for the trouble.
    With 2.6., the HTML standard for the generated HTML file changed from HTML 4.01 Transitional to HTML5. HTML5 does not allow (or discourages) style attributes in the HTML code. Therefore the previously used <table border="1" cellpadding="2" frame="box"> cannot be used anymore. The default border width is 0, so tables have no borders unless style information is provided with CSS. All style information is now in the file "metaf2xml.css", referenced by the generated HTML file. With the CSS file, the HTML output looks identical in 2.5 and 2.6 in browsers capable of using CSS.
    You can use the CSS file as follows.
    The HTML file generated by "metaf.pl" references the CSS file as "../metaf2xml.css", i.e. it is expected in the parent directory. (This is mainly due to the setup of the SourceForge environment for the project web service.) If you do not want to modify "metaf.pl", the generated HTML files should be put into some subdirectory of the directory where the file "metaf2xml.css" resides.
    Alternatively, replacing the line
    <link rel=stylesheet type=text/css href=../metaf2xml.css>
    with e.g.:
    <link rel=stylesheet type=text/css href=metaf2xml.css>
    in "metaf.pl" would allow to store the CSS and HTML files in the same directory.

    HTH.
    Kind regards
    Thomas

     
  • Anonymous

    Anonymous - 2020-04-17

    Hey Thomas
    That did it. Thank you very much.

    If I could just ask one more question? I can not process buoy data by ids never could even on Debian. I can parse a buoy message by not by ID's. Something like [ perl metaf.pl format=html lang=en type_buoy=wmo src_buoy=wmo msg_buoy="41007 44013" >abc.html ] like evrything else. What am I doing wrong?

    Thanks

    Phil

     
    • metaf2xml

      metaf2xml - 2020-04-18

      Hi Phil,

      if buoy ids (or ids for METAR/TAF, SYNOP, or AMDAR) are specified, a data source is required to provide messages for them. I assume that you do not have a local database or local files which contain weather messages, so the command line option "src_buoy" is used to select the data source. "wmo" was given as its value, but this value is not recognised, so the default value "nws" is used to fetch data from files in https://tgftp.nws.noaa.gov/SL.us008001/DF.an/DC.sfmar/DS.dbuoy. This data source does not have data for the buoy ids 41007 or 44013. To check that the program works with this data source you could try the buoy ids 41730 or 44857, the program should display recent weather messages for them.

      Kind regards
      Thomas

       

      Last edit: metaf2xml 2020-04-18
  • Anonymous

    Anonymous - 2020-04-18

    Hey Thomas,
    Looks like my own sloppiness is at fault here . Works like a charm.
    Thanks again, Phil

     
    • metaf2xml

      metaf2xml - 2020-04-18

      Hi Phil,

      no problem, thanks for the feedback.

      Kind regards
      Thomas

       

Anonymous
Anonymous

Add attachments
Cancel





Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.