You don't have to export the translations — BabelEdit works directly on your JSON/XLF/YAML or whatever file format you use.
The .babel file contains the project configuration, the languages you've set up, the files to edit and meta information that can't be directly saved in the translation files auch as the approved flag and comments.
You can export the translations as CSV or Excel (.xlsx) — every professional translator should be able to work with these files. You can import the translations back into your project later.
Send her/him the .babel file and the translation files (JSON/XML/YAML) you use. Make sure that everything is in the same relative position to the .babel file.
Google's web translation is free — that's right — but not the translation API we have to use in BabelEdit. We have to pay Google for this service. Same as for Microsoft and DeepL
With Pre-Translate or Suggestions in BabelEdit, Translation Credits are used based on the number of characters in the translation string. For example, "Hello" counts as 5 credits.
ConsistencyAI is more costly and its exact credit consumption can't be predicted upfront. It analyzes both primary and target language text, modifies it and provides explanations for the changes. The AI service bills us for characters sent and received. As the proposed changes are unknown beforehand, we can only offer a rough estimate, based on similar past requests. The final number of credits charged correlates with the actual cost from the AI service and may vary from our estimate.
Neither. Translation Credits come with your license and are not time-limited. You can purchase more credits if you've consumed all your initial ones.
The Translation Credits are shared among all users using that license.
No. Unfortunately, that's currently not possible.
Yes. This is because we need to submit the text to both services, which costs us credits for both translations.
The license works on Mac, Windows and Linux. You can use it as long as you are the only person using it and you don't install it on more than 2 computers.
Please send the following information: Your name, email address used for the purchase, time of purchase.Do not sendyour credit card details.
Use **Deactivate license** inside the application's menu on your old computer and activate the license on the new system.
If you can't reset the license anymore visit the License Manager.
You can uninstall the license once within 14 days. Swapping the licenses between multiple computers does not work.
You can uninstall the license once within 14 days - sorry that we have to put this restriction on you but we had too many companies buying one license and using it with multiple accounts. If you are not swapping licenses between accounts contact us to release the license.
You can use BabelEdit on up to 2 computers as long as you are the only person using it. In case you need to run BabelEdit on additional computers contact us.
You'll receive an email with the invoice some time after the purchase. The email is sent from 2checkout.com / 2co.com or verifone.com.
In case you did not receive that email after some time please take a look at the next section Where can I get my invoice?
I assume that you've already looked in your spam folders... so here's how to access the invoices: I can not directly send you an invoice since you did not make the purchase from use directly but from our reseller 2checkout / Verifone.
You can access the invoice from their customer portal which you can find here: https://secure.2co.com/myaccount You can use the account to:
When you access it for the first time, go to "Create new account" and enter the email address that you have used to order. You will then receive an email from Verifone containing a link to setup your password.
You can also log-in to their account with your Google, Yahoo or AOL e-mail address.
No, I can't. Sorry. This is because you are not directly purchasing from us, but from out reseller and I can't change their invoices.
Please contact support@2checkout.com for this - I would only delay the whole process forwarding emails between you and them.
Yes - but not from us. We are not selling our products directly. You are purchasing them from our reseller 2checkout who handles purchases, invoicing and tax. You'll have to ask them for the document.
Please understand that we are software developers and no experts in international law. Our current license agreement was created by a lawyer. We can't simply change parts of it but I can give you a custom license agreement following this procedure:
Sorry — I don't see why you would need an NDA. We are not at all interested in your internal company structure, projects or whatsoever. Product prices are publicly available on our webpage. We of course honor your privacy: We don't talk to any 3rd party about our customers, or disclose your identity without your consent. In short: There's nothing confidential to talk about.
If you still need and NDA please understand that we are software developers and no experts in international law. We'll have to let our legal consultant have a look at the NDA before signing it. This creates some cost which in many cases exceeds the value we get in return for our license sales. We charge 750€ upfront before we start reading your NDA. The 750€ do not guarantee that we sign the NDA.
Yes, there is a 7-day trial mode with unrestricted features. After that period BabelEdit requires a license key.
The license agreement is accessible via the menu in BabelEdit or online here. Additionally you can find it inside BabelEdit's program folder (Windows) or inside BabelEdit's .app bundle.
No. BabelEdit currently only supports a subset of XLIFF 1.2 that is also supported by @angular/localize.
Not fully. BabelEdit is no XLIFF editor. We focused on the features required to edit files extracted with @angular/localize.
The currently fastest way to do this is to delete the file on your file system. BabelEdit reloads the file as an empty when you activate BabelEdit's window. Pre-translate now fetches all translations for that file.
BabelEdit stores files with local file endings. That means LineFeed (LF) on macOS and Linux, CarriageReturn-LineFeed (CRLF) on Windows.
If you are using in a mixed environment with Windows and macOS or Linux clients, you should configure your license management system to convert between the different ending styles. See our tutorial How to handle line endings in git for more details about how you can do that.
Only in the user interface. All paths are stored relative to the project (.babel) file to make them portable across computers and operating systems. If you check the .babel file into your version management system together with your translation files everything should work when you check it out on another system.