Parseable METADATA files

lishaman / googlefontdirectory

Automatically exported from code.google.com/p/googlefontdirectory

0 stars 0 forks source link

What steps will reproduce the problem?
1. Attempt to load METADATA files using a standard YAML parser.
2. YAML parser fails to load some files due to syntax errors.

As far as I can tell the METADATA files were intended to be valid YAML files, 
however there are some files in the repository which are not valid. I have 
created a clone which fixes some of the more rare issues that I am aware of, 
located at http://code.google.com/r/matt-yaml-fixes/.

However there are many METADATA files which contain multiline descriptions with 
contain colons, which isn't valid YAML. It would be easy to fix this by 
changing all multiline descriptions to use a single set of double quotes which 
is indented and remove the the trailing slashes. However this would be a style 
change that should be implemented across the entire repository so I didn't 
include it in my clone. What are you thoughts on this change? It would 
considerably simplify parsing by others.

Original issue reported on code.google.com by m...@typekit.com on 24 Feb 2012 at 10:59

Matt, thanks for this report! However the METADATA files aren't intended to be YAML, they are in fact simple Java Properties files - http://docs.oracle.com/javase/7/docs/api/java/util/Properties.html#load(java.io. Reader) - the reasons for which are clear from the current 404 page http://www.google.com/webfonts/404 ;) Indeed I have suggested moving to YAML in the past, but sadly the GWF engineering team must focus on the highest impact engineering work, and perhaps your language has library support for JP syntax :-) I've passed this on to the team, but I'm marking this as 'wontfix' as I think its unlikely to be changed. Thanks again though :)

lishaman / googlefontdirectory

Parseable METADATA files #120