Skip to content

File format for interchange #6

@abourget

Description

@abourget

Sending files for translation to upstream service providers is a common task. Right now, all my translations are directly in my Go code. I will soon need to send it out.. is there any format in which we could pass all the semantics of universal-translator, back and forth ?

This site lists a bunch of them (in which go-i18n figures!):

https://phraseapp.com/docs/guides/formats/

Perhaps we can pick one that is used in the industry ?

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions