It is normal to expect that in some languages strings might be some 50% longer, but even 200% is not much unusual. That is why all components must have the Autosize property set to True. Let's convert this application to support translation into German.ĭuring design of the GUI it shall be considered, that a string will have a different length in each language. You'll see a typical application with a menu and some controls to show a file list and the selected image. Open the project file imgview.lpi, compile and run it. In order to keep the original, copy the entire project folder into a separate directory, e.g. Looking through the example projects that come with Lazarus I found that examples\imgviewer may be a decent demo project. There will be some notes here and here to identify the differences between the versions.Īt first, we need an application that we want to translate. Therefore I'd urge you to read the wiki articles Localization and/or Translations_/_i18n_/_localizations_for_programs which explain the basic fundamentals behind the scene.īefore starting, I'd like to mention that this tutorial was initially written for Lazarus version 1.2 and now has been updated to version 1.4. But it may be a good idea to learn something about the basic ideas behind that architecture. I'd like to share this information with interested users of Lazarus. Then I found out that is is amazingly simple once I understood the first steps. Preparing applications for several languages has always been a bit of a mystery to me - until I finally tried. 5 Use LCLTranslator unit (class TDefaultTranslator). Poedit add source key android#Can be used to export in Android XML format without wrapping the strings in quotes. The value must be a json array of objects. Set specific advanced options for particular formats (where these exist). Set it to terms to order results by 'terms' alphabetically.įilter results by tags you can use either a string for a single tag or a json array for one or multiple tags (example) Set it to 1 to mark corresponding translations from the other languages as fuzzy for the updated valuesįile format arb, csv, ini, key_value_json, json, po, pot, mo, properties, resw, resx, ts, apple_strings, xliff, xliff_1_2, xlf, xmb, xtb, rise_360_xliff, xls, xlsx, android_strings, yml įilter results by 'translated', 'untranslated', 'fuzzy', 'not_fuzzy', 'automatic', 'not_automatic', 'proofread', 'not_proofread' (only available when Proofreading is set to "Yes" in Project Settings) you can use either a string for a single filter or a json array for one or multiple filter (example) xliff format only - set it to 1 if you want to import translations from the source tag Ignored if updating = translations.Īdd tags to the project terms available when updating terms or terms_translations you can use the following keys: "all" - for the all the imported terms, "new" - for the terms which aren't already in the project, "obsolete" - for the terms which are in the project but not in the imported file and "overwritten_translations" - for the terms for which translations change (example)įor. Set it to 1 if you want to sync your terms (terms that are not found in the uploaded file will be deleted from project and the new ones added). Set it to 1 if you want to overwrite translations Poedit add source key code#The language code (Required only if updating is terms_translations or translations) xls or any of the supported file formats) Terms | terms_translations | translations Request examples included for the following: C sharp, Go, Java, jaxrs-cxf-client, kotlin-client, Php, Python, Scala, Swift3, Swift4, Swift5, typescript-angular, typescript-fetch. Poedit add source key download#You can find the document on SwaggerHub or download POEditor's Swagger file, which can "translate" our API for your specific needs. POEditor's API has an OpenAPI specification. If you think the key has been compromised, you can reset it from Account Settings > API Access by clicking the Regenerate API Token button, or you can delete the API Access using the Remove API Token button. You'll find it in Account Settings > API Access. You can get this key from your POEditor account. AuthenticationĪll requests to the API must contain the parameter api_token. If the response is not sucessful, the JSON object will contain an error code and a message. The response you'll get will be a JSON encoded object. Some endpoints will require you to send the parameter values as JSON.Īn example of a properly formatted JSON, for a request to export to Android Strings with unquoted strings using the «options» parameter: Īn example of a request containing this JSON: curl -X POST \ The POEditor API consists of a set of callable methods. To perform an action using the API, send a request to the API endpoint and a response will then be sent back to you.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |