php-translation / documentation Goto Github PK

Documentation for "Extracting Translations from Source" is incomplete.

This makes it difficult to work with the package.

According to the specification - http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#Struct_Grouping
the format of .xliff or .xlf files should have 'trans-unit' whereas the extract commands outputs with just 'unit'.
This means that I cannot update my translation files that I have stored with CrowdIn.

Hello, is it possible to auto-add the missing translations and have the bundle translate them using Google Translate in order to have a "baseline" for better translations?

Thanks.

Let's add a link to the http://php-translation.readthedocs.io/en/latest/ in the repo description.

Now I see only:

No description, website, or topics provided.

The blacklist_domain/blacklist_domains config options are a little-known fact, we need to disclose it in docs.

In this page : /blob/master/symfony/auto-add-missing.rst

There's a workaround to make "auto_add_missing_translations" working in prod.

However, in symfony 4.2 that workaround does not work in any config file (that I am aware of) and breaks the config.

Note that everything work well in DEV with the profiler enabled.

My env :
-ubuntu

• php 7.2
• symfony 4.2.*
• "symfony/translation": "4.2.*",
• "php-translation/symfony-bundle": "^0.8.1",

Hello,

First of all, thank you for your work, I'm trying to get it working on a project and so far it's going well. I've found your bundle in a comment you made here.

I just wanted to understand something as I've not found it in the Symfony doc :

• translations keys are fetched from PHP and Twig files (as said in config file), so the config entry dirs is not meant to point directly at a translation folder like src/AppBundle/Resources/translations. Is that correct ?
• in that way, how can translations be filled from already written translations ? For example, I'm writting my translations in a YAML file in my bundle. Is there a config key to use those ?

Thank you.

I think we must use RequestMatcher to enable aggressive caching only for google translate.

We should tell the world how to do translations. IE how to structure the translations keys.

Example:
https://developer.happyr.com/how-happyr-work-with-symfony-translations

Hi,
Your site https://php-translation.readthedocs.io/ is out of date, to the content in the repository

Hello!

This is not an issue, but I couldn't open a PR for this.

With my previous symfony bundle (jms) I was able to translate my routes for different languages.
/contact = /kontakt = /contacto = etc.

Is there a config for enabling this feature or is it planned?

thx in advance