support exporting to other storage-formats

[earloc]

As a developer, when I export typealized interfaces, I want to specify a format other than Resx, to leverage code-first-i18n in conjuntion with other storage-formats for translations.

[ivanhofer]

I have the same issues in typesafe-i18n and want to solve them with pipeli18ne. What I have thougth about is having an object-like representation of a message and then using a "serialize" function to convert them to a specific format. Those serializers can convert from the object representation to the message format and the other way around. It is easy to replace a serializer with another one. The runtime code at the end only knows about the objects and not about a specific message format.

[earloc]

Hmmm, need to think about this. So in short, if my CLI where able to export to such a metadata-repsentation(as stated in this comment ), I´d be ready to leverage whatever tooling experience may pop up there over at [pipeli18ne] in the future...

Toughest topic currently is to sync with existing resources #93, actually.

Still need to find a way how to best support theses scenarios, prior thinking about other formats, though.