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

Finish application translation #80

Merged
merged 11 commits into from Jul 7, 2015
Merged

Finish application translation #80

merged 11 commits into from Jul 7, 2015

Conversation

javiereguiluz
Copy link
Member

This fixes #8 thanks to the work made by @b-durand in #78.

@javiereguiluz
Copy link
Member Author

The reorganization of the English translation is now complete. Please review it before I make the needed changes in the rest of translations. Thanks.

@OskarStark
Copy link
Contributor

@javiereguiluz if this is merged i will do the german translation if you like and if useful

@javiereguiluz
Copy link
Member Author

@OskarStark great! That would be awesome.

@OskarStark
Copy link
Contributor

ok 😄

@javiereguiluz
Copy link
Member Author

I have a question about the names of the translation strings related to the entity validation.

I've defined them as follows, but I don't like it:

<trans-unit id="entity.comment_blank">
    <source>entity.comment_blank</source>
    <target>Please don't leave your comment blank!</target>
</trans-unit>
<trans-unit id="entity.comment_short">
    <source>entity.comment_short</source>
    <target>Comment is too short ({{ limit }} characters minimum)</target>
</trans-unit>
<trans-unit id="entity.comment_long">
    <source>entity.comment_long</source>
    <target>Comment is too long ({{ limit }} characters maximum)</target>
</trans-unit>
<trans-unit id="entity.comment_invalid">
    <source>entity.comment_invalid</source>
    <target>The content of this comment is considered spam.</target>
</trans-unit>
<trans-unit id="entity.summary_blank">
    <source>entity.summary_blank</source>
    <target>Give your post a summary!</target>
</trans-unit>
<trans-unit id="entity.post_short">
    <source>entity.post_short</source>
    <target>Post content is too short ({{ limit }} characters minimum)</target>
</trans-unit>

What do you think of replacing it by the following?

<trans-unit id="comment.blank">
    <source>comment.blank</source>
    <target>Please don't leave your comment blank!</target>
</trans-unit>
<trans-unit id="comment.too_short">
    <source>comment.too_short</source>
    <target>Comment is too short ({{ limit }} characters minimum)</target>
</trans-unit>
<trans-unit id="comment.too_long">
    <source>comment.too_long</source>
    <target>Comment is too long ({{ limit }} characters maximum)</target>
</trans-unit>
<trans-unit id="comment.is_spam">
    <source>comment.is_spam</source>
    <target>The content of this comment is considered spam.</target>
</trans-unit>
<trans-unit id="comment.blank_summary">
    <source>comment.blank_summary</source>
    <target>Give your post a summary!</target>
</trans-unit>
<trans-unit id="post.too_short">
    <source>post.too_short</source>
    <target>Post content is too short ({{ limit }} characters minimum)</target>
</trans-unit>

@OskarStark
Copy link
Contributor

👍 for shorter version!

@b-durand
Copy link
Contributor

b-durand commented Jul 6, 2015

@javiereguiluz the domain is validators and not messages for constraints.

@javiereguiluz
Copy link
Member Author

@b-durand I can't believe I made this mistake :'( This morning I saw that translation wasn't working for validation ... but I didn't realize this issue. Thanks for telling me! It's fixed now.

@b-durand
Copy link
Contributor

b-durand commented Jul 6, 2015

We should also localize the date format for "commented on". I regret to have choice with only 4 formats instead of format pattern for skeleton 😞

@javiereguiluz
Copy link
Member Author

@b-durand I'm not sure I understand your last comment about date internationalization.

@OskarStark
Copy link
Contributor

i think @b-durand would say, that in englisch we use 01-01-2015 and in german `01.01.2015``

@javiereguiluz
Copy link
Member Author

OK, I understand now. Thanks. Let's do that change in a separate PR because it needs to install the Twig extensions and all that.

@javiereguiluz
Copy link
Member Author

@b-durand this feature is finally merged. Thanks a lot for working on this!

@javiereguiluz javiereguiluz merged commit 4e677a3 into symfony:master Jul 7, 2015
javiereguiluz added a commit that referenced this pull request Jul 7, 2015
This PR was merged into the master branch.

Discussion
----------

Finish application translation

This fixes #8 thanks to the work made by @b-durand in #78.

Commits
-------

4e677a3 Finished French translation
e291f99 Moved french validation translators to its own file
df556d3 Fixed some translation errors
7c6e0ed Updated the translation strings related to validation
7770358 Finished reorganizing app translation
9c9f176 Reordered some items and removed duplicates
b7dd618 Use XLIFF format only and made some tweaks to translation files
b8e40c4 Update the French tranlations
85ee456 Translate constraint messages in Yaml file
f2c44f5 Replace the English translations by key
35f2784 Fix domain for error messages
@javiereguiluz
Copy link
Member Author

@OskarStark this feature is finally merged, so you can update the German translation if you have some free time. Thanks!

@javiereguiluz javiereguiluz mentioned this pull request Jul 7, 2015
9 tasks
@@ -32,14 +32,16 @@ public function buildForm(FormBuilderInterface $builder, array $options)
// for the full reference of options defined by each form field type
// see http://symfony.com/doc/current/reference/forms/types.html
$builder
->add('title')
->add('summary', 'textarea')
->add('title', null, ['label' => 'label.title'])
Copy link
Member

Choose a reason for hiding this comment

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

this is not compatible with php 5.3 (as stated in composer.json). so I'd suggest increasing the php requirement for the demo. we do not need to support 5.3.

Copy link
Member Author

Choose a reason for hiding this comment

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

Good catch! I'm going to check of non-PHP 5.3 features and I'm going to setup a .travis.yml file so we can check on any PHP version. Thanks!

Copy link
Contributor

Choose a reason for hiding this comment

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

CI with Travis will be a great!

@xabbuh xabbuh mentioned this pull request Jul 8, 2015
javiereguiluz added a commit that referenced this pull request Jul 27, 2015
This PR was merged into the master branch.

Discussion
----------

Romanian translation

Romanian translations based on #80

Commits
-------

4b89fbc Romanian translation
@ben29
Copy link

ben29 commented Aug 12, 2016

i can do for Hebrew
still needed?

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.

Finish application internationalization
6 participants