8000 Make language file name configurable in translation component · Issue #27644 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content
Make language file name configurable in translation component #27644
Closed
@DanielSiepmann

Description

@DanielSiepmann

Description
In v4.1.0 the file name of XLIFF files is linted to contain the language as suffix. So locallang.de.xlf would be valid, while de.locallang.xlf would not be valid.

That might be fine for Symfony projects. But there are other projects out there also using XLIFF for translations. In TYPO3 CMS for example the order is different. To still use the translation component to validate XLIFF files for other projects, like TYPO3 CMS, I would suggest to make this configurable. By keeping the old behaviour as default this would be a non breaking change.

As a benefit the component can work as a Linter in further projects and might get further contributions.

Example
An example call with configurable position might be:
php lint:xliff --filename-language-position prefix <filename>

I would be happy if this change sounds reasonable. It shouldn't be a huge thing.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0