New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fail on ":" character #113

Closed
smercier opened this Issue May 20, 2015 · 2 comments

Comments

Projects
None yet
3 participants
@smercier
Contributor

smercier commented May 20, 2015

Scribe fail on ":" character.

WEB {
        METADATA {{
            "ows_enable_request"   "*"
            "wms_srs"   "EPSG:900913 EPSG:4326 EPSG:3857"
            "labelcache_map_edge_buffer"   "10"
            "wms_title"   "grid"
        "wms_onlineresource"    "http://mapserver.com:8081/cgi-bin/mapserv?map=/opt/scribeui/workspaces/blabla.map"    
        }}
        IMAGEPATH: '/tmp/ms_tmp/'
        IMAGEURL: '/ms_tmp/'
    }

give error:

[Tue May 19 21:04:06 2015].231654 getString(): Symbol definition error. Parsing error near (:):(line 20)

but this work:

"wms_onlineresource"    "mapserver.com/cgi-bin/mapserv?map=/opt/scribeui/workspaces/blabla.map"   
@dmorissette

This comment has been minimized.

Show comment
Hide comment
@dmorissette

dmorissette May 20, 2015

Member

To help troubleshoot this, I suggest that whoever works on this look at the output of scribe.py on that mapfile fragment. It is very likely that the scribe.py script truncates the string at the ":" which results in an invalid mapfile as output.

The solution would likely be to have the scribe.py parser honor strings when it looks for ":".

Member

dmorissette commented May 20, 2015

To help troubleshoot this, I suggest that whoever works on this look at the output of scribe.py on that mapfile fragment. It is very likely that the scribe.py script truncates the string at the ":" which results in an invalid mapfile as output.

The solution would likely be to have the scribe.py parser honor strings when it looks for ":".

@samuellapointe

This comment has been minimized.

Show comment
Hide comment
@samuellapointe

samuellapointe May 20, 2015

Contributor

The problem comes from Scribe removing comments, so anything starting with //. I am working on a fix right now.

Contributor

samuellapointe commented May 20, 2015

The problem comes from Scribe removing comments, so anything starting with //. I am working on a fix right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment