Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Indentation mess in ultilines translations using PHP dumper #192

Closed
wanjee opened this issue Apr 9, 2014 · 2 comments
Closed

Indentation mess in ultilines translations using PHP dumper #192

wanjee opened this issue Apr 9, 2014 · 2 comments

Comments

@wanjee
Copy link

wanjee commented Apr 9, 2014

Hi,

I have translations that contains multiple lines of HTML. When I extract to the translations several times to PHP format I see that the indentation of those lines is increased on each extract.

The command I use is

php app/console translation:extract --bundle=MyNiceBundle --output-format=php en

As an example if I have a "page.about.content" key the file looks like this after I first translated the string :

return array(
    'page' => array(
        'about' => array(
            'content' => '
<h1>My title</h1>
<p>Some content</p> 
<p>Some more content</p>
',
        ),
    ),
);

On each extract operation it will add 16 spaces in front of each line, making it a nightmare for translators to edit. As an example after 4 iterations the file look like this :

return array(
    'page' => array(
        'about' => array(
            'content' => '
                                                                <h1>My title</h1>
                                                                <p>Some content</p> 
                                                                <p>Some more content</p>
                                                                ',
        ),
    ),
);

I tried to investigate it a bit but I don't get it. Am I missing some configuration ?
Is this an issue ?
Thanks !

W-)

@Nyholm
Copy link
Collaborator

Nyholm commented Mar 24, 2016

Thank you for reporting this. This issue is very old, do you have the same problem with the latest release?

@Nyholm
Copy link
Collaborator

Nyholm commented Aug 4, 2016

Im closing this because of inactivity. Feel free to reopen a new issue.

@Nyholm Nyholm closed this as completed Aug 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants