thomas-darling / gulp-translate Goto Github PK

Is it possible to automatically replace the translate tag with translation="unique id" so the id's match the id's in the exported json file?

So to extract something like this:
<h1 translate>Etiam rhoncus. Maecenas tempus</h1> <h2 translate>Lorem ipsum dolor sit amet, consectetuer adipiscing elit.</h2>

And automatically replace translate with a attribute + id:
<h1 t="211d76eec">Etiam rhoncus. Maecenas tempus</h1> <h2 t="96f37e421">Lorem ipsum dolor sit amet, consectetuer adipiscing elit.</h2>

This way I can easily combine it with aurelia-i18n which looks for the "t" attribute.

Thanks,
PP

Add support for the industry standard XLIFF format, to eliminate the need for format conversion when integrating with existing translation management systems.

The current support for templating languages is limited to binding expressions.
Would be cool if it could be expanded to also support PHP and Razor templates.

In the readme, we currently hint that one way of dealing with large pieces of content, which is probably better stored in a CMS, could be to export such content from the CMS into a json content file, from which it can then be imported into templates using the import command.

While this definitely works, it would be easier and more flexible to actually have an extension point in the form of a missingContentHandler property on the import config. That way, a custom function can be specified for handling content not found in the import file. This function should return either the content, if found, or undefined if not found. Alternatively, it should return a promise, which will either be resolved with the content, if found, or rejected if not found.

When exporting content, we currently add a source path for each file in which a content instance is found. Ideally though, we should add a source path for each content instance, ideally including the line and column numbers for the beginning and end of the content.

Hi,

I'm currently using your great plugin for multilanguage/multi tenant frontend and experienced
two difficulties:

1. If I want to translate single generic word or currencies in sentences I have to add a tag like $.

Could it be possible to also support a configurable tag like <translate>$</translate> which will get completely replaced to $ respectively € etc?
This would help to reduce the markup and to solve issues when spans ord divs are styled via css.

2. If I want to translate attributes like href I can use href.translate.
   But sometimes I need to translate <a href="mailto:[email protected]">[email protected]</a>.

My approach end like this <a href.translate href="mailto:[email protected]" translate>[email protected]</a> with two entries in my language file for
mailto:[email protected] and [email protected]. Do i miss here something?
Maybe we can use something like this to address the redundancy : <a mailto.href.translate href="mailto:[email protected]" translate>[email protected]</a> with only one entry to the language file (without the mailto: prefix).

Thanks you for your beautiful and helpful plugin!

Angular 2 supports annotating content by placing a comment before and after the content that should be exported. We should consider whether adding a similar feature to this plugin would be a good idea.