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

GB Locale files #1438

Closed
wants to merge 5 commits into from
Closed

GB Locale files #1438

wants to merge 5 commits into from

Conversation

hillzzz
Copy link

@hillzzz hillzzz commented Jul 3, 2015

I have written the GB Locale files and inserted them into what I hope are the correct locations - these turn "Tax" into "VAT" "Cart" into "Basket" and enable UK English specific spellings etc. I hope it will help UK specific sites to get started more quickly. Thanks. Hillary

@joshdifabio
Copy link
Contributor

Good job! It'd probably be helpful if you committed the US English files first and then committed again with your changes; that way it'd be easy to see what you've changed :).

@hillzzz
Copy link
Author

hillzzz commented Jul 3, 2015

Ah Ok - I will know for next time.

I have not made any changes to the en_US files - all the changes I have made are in directories called “en_GB” so it should be clear as these directories don’t exist in the original Magento2 repository.

in other words if its in a directory called en_GB its mine and there are approximately 78 files.

Cheers

Hillary
07919 488425
zen71001@zen.co.uk

On 3 Jul 2015, at 17:06, Josh Di Fabio notifications@github.com wrote:

Good job! It'd probably be helpful if you committed the US English files first and then committed again with your changes; that way it'd be easy to see what you've changed :).


Reply to this email directly or view it on GitHub #1438 (comment).

@hillzzz
Copy link
Author

hillzzz commented Jul 3, 2015

So its additional files in the i18n/magento https://github.com/magento/magento2/tree/develop/app/i18n/magento directories, that I have added - path is for example, /app/i18n/magento https://github.com/magento/magento2/tree/develop/app/i18n/magento/en_gb/
I have just submitted another pull request because I missed an en_GB.csv file in app/code/Magento/Checkout/i18n/ https://github.com/hillzzz/magento2/commit/f1cd1df930dee16baab28d53d23ddf6a7f79195fen_GB.csv which is now added.

Cheers,

Hillary
07919 488425
zen71001@zen.co.uk

On 3 Jul 2015, at 17:06, Josh Di Fabio notifications@github.com wrote:

Good job! It'd probably be helpful if you committed the US English files first and then committed again with your changes; that way it'd be easy to see what you've changed :).


Reply to this email directly or view it on GitHub #1438 (comment).

@magento-cicd2
Copy link
Contributor

We have automated a Magento Contributor License Agreement verifier for contributions sent to our GitHub projects.
Please see the CLA agreement in the Pull Request comments.

@Vinai
Copy link
Contributor

Vinai commented Nov 3, 2015

The new required registration.php file that was introduced a few weeks back is missing, registering the locale with the component registrar. Otherwise the one failing integration test might not be directly caused by the new theme, but the reason for the failure needs to be researched.
Can you please update the PR accordingly? Thanks you!

@benmarks
Copy link
Contributor

benmarks commented Nov 9, 2015

@hillzzz Please check the CLA requirement & @Vinai's comment.

@KrystynaKabannyk
Copy link

Hi @hillzzz, are you still interested in your pull request? If yes, could you please sign License Agreement and update information?

@davidalger
Copy link
Member

Closing due to lack of reply from OP.

@davidalger davidalger closed this May 13, 2016
magento-team pushed a commit that referenced this pull request Sep 1, 2017
Bugs
- MAGETWO-67092 Table salesrule_product_attribute is not populated when upgrading to 2.2
- MAGETWO-70540 Edit bundle product from shopping cart work unexpected
- MAGETWO-67037 core_config_data table is not populated correctly when upgrading from 2.1 to 2.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants