Skip to content
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

Enhancement: Additional file formats for localizations #46

Open
2 of 9 tasks
EliteMasterEric opened this issue Dec 31, 2021 · 1 comment
Open
2 of 9 tasks

Enhancement: Additional file formats for localizations #46

EliteMasterEric opened this issue Dec 31, 2021 · 1 comment

Comments

@EliteMasterEric
Copy link
Collaborator

EliteMasterEric commented Dec 31, 2021

There are a variety of file formats available for storing and using translations, and Firetongue should support more of them.

This checklist is based on the list of file formats available for export from POEditor.com, an online localization platform.

  • Comma-separated values (.csv)
"flag","content",
"$HELLO_WORLD","Hello, World!",
"$TEST_STRING","My mom took the elevator to the defense department.",
  • Tab-separated values (.tsv)
flag	content
$HELLO_WORLD	Hello, World!
$TEST_STRING	My mom took the elevator to the defense department.
  • Android String Resources (.xml)
<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string name="hello-world">"Hello, world!"</string>
    <string name="test-string">"My mom took the elevator to the defense department."</string>
</resources>
  • Key-Value JSON (.json)
{
    "hello-world": "Hello, world!",
    "test-string": "My mom took the elevator to the defense department."
}
  • Term JSON (.json)
[
    {
        "term": "hello-world",
        "definition": "Hello, world!",
        "context": "",
        "term_plural": "",
        "reference": "",
        "comment": ""
    },
    {
        "term": "test-string",
        "definition": "My mom took the elevator to the defense department.",
        "context": "",
        "term_plural": "",
        "reference": "",
        "comment": ""
    }
]
  • GNU gettext (.po, .pot, .mo)
msgid ""
msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: POEditor.com\n"
"Project-Id-Version: Test2\n"
"Language: en\n"

#: 
msgid "hello-world"
msgstr "Hello, world!"

#: 
msgid "test-string"
msgstr "My mom took the elevator to the defense department."
  • YAML (.yml)
hello-world: Hello, world!
test-string: My mom took the elevator to the defense department.
  • Apple Strings (.strings)
"hello-world" = "Hello, world!";
"test-string" = "My mom took the elevator to the defense department.";
  • Microsoft Resource (.resx)
<root>
  <!-- HEADER HERE -->
  <data name="hello-world" xml:space="preserve">
    <value>Hello, world!</value>
  </data>
  <data name="test-string" xml:space="preserve">
    <value>My mom took the elevator to the defense department.</value>
  </data>
</root>
@EliteMasterEric
Copy link
Collaborator Author

See https://poeditor.com/help/#SupportedFormats for some common formats, although we should probably focus on the most popular ones to minimize development time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant