Different format support for one file export

[OO00O0O]

Add format selection to translation export for one file.
Currently there are none. You can download file only in default format you have uploaded.

[rubyluk]

Hi thank you for the suggestion.

May I know any particular format conversions you need when using OneSky?
Would it be a one-off conversion or a constant difference on file formats between your imported files and translation files?

[OO00O0O]

Constant diff. PHP <-> JSON(node.js applications) would be nice and PHP<-> YAML(symfony2).

[QuadRatNewBy]

Just adding my two cents.
Every file looks like "Key-Value Pair" (At least those that I've saw). So I think it would be great to have ability to download translation in simplest format - 'key' = 'value' (Similar to INI or TEXT_INI formats).
Having this in hands one can easily write their own custom converter (even to 'non-onesky' formats).

[vanniktech]

+1 what's the status for this one, currently I can only download the files in the format of iOS (since it's the default one for the project). I want to be able to download them in the Android format (XML) though.

[mickaelbeaudry]

+1 on @vanniktech's comment, same here

[TriPhoenix]

I'd like to +1 this issue as well; in our specific case the original data is an xlsx file while we need an iOS .strings export; Unfortunately I cannot even download them as .xlsx right now as those are supposedly not downloadable through the API (error message).

[FranzBusch]

+1 same here

[ab9-er]

Facing the same issue, guess it is still open after 2 years without any resolution. Any updates @rubyluk ?

[timothycosta]

Same issue. We would like to share strings between ios and android, but can only download .strings via the API.

[marijnvandevoorde]

+1 here. simply because I18NEXT_HIERARCHICAL_JSON does not fill out fallbacks (contrary to documentation), so I want to export using that instead of the default HIERARCHICAL_JSON.

The closest I can get today is export to I18NEXT_MULTILINGUAL_JSON, which will not fill out fallbacks (we want to do fallbacks ourselves because we don't want to fallback straight from fr-FR -> base language, instead, we want to go from fr-FR to fr to en to base) and then split up. That's not working well for us.

[marijnvandevoorde]

By the way, this is a duplicate of #7

[mtter]

Same/similar problem here: File format (.csv (Comma Separated Values)) is not downloadable through API

[bendiknesbo]

How can this not have been added yet?
Please add format, similar to the "format" parameter in the Classic API's "/string/download"

[oleghnidets]

Hi guys,
Any updates on this? It would be great feature. It stops us from using API.