Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Translation] added xliff loader/dumper with resname support #7304

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

Closed
wants to merge 3 commits into from

Conversation

jfsimon
Copy link
Contributor

@jfsimon jfsimon commented Mar 8, 2013

Q A
Bug fix? no
New feature? yes
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #5940

*
* @author Jean-François Simon <[email protected]>
*/
class XliffFileDumper2 extends XliffFileDumper
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol not really or?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Tobion could you be more specific?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The class name is not really expressive by just adding a number at the end.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These bad names are a sort of request for proposals...
Something to propose?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well then you should mark the PR as WIP for the time beeing.

@jfsimon
Copy link
Contributor Author

jfsimon commented Mar 8, 2013

@Tobion what do you think of XliffFileWithResnameDumper and XliffFileWithResnameLoader?

@robinduval
Copy link
Contributor

💯 great idea !

@materazu
Copy link

materazu commented Mar 8, 2013

🌟 better.

@saro0h
Copy link
Contributor

saro0h commented Mar 8, 2013

👍 Can't be worse than the previous one

@dxb
Copy link

dxb commented Mar 8, 2013

+1

@Tobion
Copy link
Contributor

Tobion commented Mar 8, 2013

@jfsimon yes the name make sense. It is not possible to add this feature without BC break?
And if not, why not simply add an option/enable method to the existing classes. Having new classes for this seems awkward to me.

@jfsimon
Copy link
Contributor Author

jfsimon commented Mar 8, 2013

@Tobion I totaly agree with you, but this has been discussed in #5940.
Does the presence of the resname attribute in the trans-unit tags represent a BC break?
Would opening another PR with this solution be a good idea?

@stof
Copy link
Member

stof commented Mar 8, 2013

Your XliffFileWithResnameLoader is able to load all files supported by XliffFileLoader so IMO you don't need to add a new class.

@jfsimon
Copy link
Contributor Author

jfsimon commented Mar 8, 2013

@stof would the resname attribute addition in the dumped XLIFF be considered as a BC break?

@jfsimon
Copy link
Contributor Author

jfsimon commented Mar 9, 2013

@stof done.
@mvrhov done.

fabpot added a commit that referenced this pull request Mar 12, 2013
This PR was squashed before being merged into the 2.1 branch (closes #7304).

Commits
-------

5bc30bb [Translation] added xliff loader/dumper with resname support

Discussion
----------

[Translation] added xliff loader/dumper with resname support

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #5940

---------------------------------------------------------------------------

by jfsimon at 2013-03-08T15:49:18Z

@Tobion what do you think of `XliffFileWithResnameDumper` and `XliffFileWithResnameLoader`?

---------------------------------------------------------------------------

by robinduval at 2013-03-08T15:49:58Z

:100: great idea !

---------------------------------------------------------------------------

by lizjulien at 2013-03-08T15:51:45Z

:star2: better.

---------------------------------------------------------------------------

by saro0h at 2013-03-08T15:52:50Z

:+1:  Can't be worse than the previous one

---------------------------------------------------------------------------

by dxb at 2013-03-08T16:00:32Z

+1

---------------------------------------------------------------------------

by Tobion at 2013-03-08T16:07:59Z

@jfsimon yes the name make sense. It is not possible to add this feature without BC break?
And if not, why not simply add an option/enable method to the existing classes. Having new classes for this seems awkward to me.

---------------------------------------------------------------------------

by jfsimon at 2013-03-08T16:17:44Z

@Tobion I totaly agree with you, but this has been discussed in #5940.
Does the presence of the `resname` attribute in the `trans-unit` tags represent a BC break?
Would opening another PR with this solution be a good idea?

---------------------------------------------------------------------------

by stof at 2013-03-08T17:01:00Z

Your XliffFileWithResnameLoader is able to load all files supported by XliffFileLoader so IMO you don't need to add a new class.

---------------------------------------------------------------------------

by jfsimon at 2013-03-08T18:21:32Z

@stof would the `resname` attribute addition in the dumped XLIFF be considered as a BC break?

---------------------------------------------------------------------------

by jfsimon at 2013-03-09T13:16:32Z

@stof done.
@mvrhov done.
@fabpot fabpot closed this Mar 12, 2013
@@ -11,6 +11,7 @@

namespace Symfony\Component\Translation\Loader;

use Symfony\Component\DependencyInjection\SimpleXMLElement;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This use statement looks wrong to me

fabpot added a commit that referenced this pull request Mar 12, 2013
This PR was merged into the 2.1 branch.

Commits
-------

ae0b8ea [Translation] removed wriong 'use'

Discussion
----------

[Translation] removed wrong 'use'

Fixes last comment from #7304 // cc @stof
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

Successfully merging this pull request may close these issues.

9 participants