Nn777 casino,Wednesday 10 April.Recharge Every day and Get Bonus up-to 50%!

Invalid locale on en_CA

Jon Wong — Fri, 20 Dec 2019 13:13:21 +0000

I noticed that the meta property for og:locate is set to en_US even when my site is set to en_CA.

language_attributes();

Shows en-CA

When i switch my locale to fr-CA og:locale does get updated.

I didn’t have a chance to view the code yet, but i assume EN is being defaulted to en-US and not taking into account other variations.

I’ve tested with and without our language plugin Bogo and see the same results.

Minor Translation Issues

Garrett Hyder — Wed, 10 May 2017 23:17:52 +0000

Hello,

While going through translations for en_CA I found a few issues;

1. Truncate your plugin description at a nicer place.
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/taxonomy-terms-order/dev-readme/en-ca/default?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=1344651&filters%5Btranslation_id%5D=49058655
String – Order Categories and all custom taxonomies terms (hierarchically) and child terms using a Drag and Drop Sortable javascript capability. No Theme updat
Better String – Order Categories and all custom taxonomies terms (hierarchically) and child terms using a Drag and Drop Sortable javascript capability.
*Note the string gets cut off halfway through the second sentence, would be nicer to just kill it after the first sentence.

2. Misspelling – Absolutelly
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/taxonomy-terms-order/dev-readme/en-ca/default?filters%5Boriginal_id%5D=1344700
String – Absolutelly, the plugin can do that. In fact you can configure so only the admin will update and the front side template will display the terms as before.
Word – Absolutelly
Should be – Absolutely

3. Misspelling – ored
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/taxonomy-terms-order/dev-readme/en-ca/default?filters%5Boriginal_id%5D=1344698
String – Yes, this is the right tool for you. The plugin come with a unique feature to update the queries on the fly and return the terms in the required ored without changing any line of code. Or as alternative you can do that manually.
Should be – Yes, this is the right tool for you. The plugin comes with a unique feature to update the queries on the fly and return the terms in the required order without changing any line of code. Or as an alternative you can do that manually.
*I also bundled two grammar things above, ‘The plugin comes with’ and ‘Or as an alternative’

4. Missing S on appear
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/taxonomy-terms-order/dev-readme/en-ca/default?filters%5Boriginal_id%5D=1344658
String – Use Taxonomy Order link which appear into each post type section to make your sort.
Should be – Use Taxonomy Order link which appears into each post type section to make your sort.

5. Gammar and Spelling ‘tose can be sorder’
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/taxonomy-terms-order/dev-readme/en-ca/default?filters%5Boriginal_id%5D=1344654
String;

Order Categories and all custom taxonomies terms (hierarchically) using a Drag and Drop Sortable javascript capability. No Theme update is required the code will change the query on the fly.?
If multiple taxonomies are created for a custom post type, a menu will allow to chose the one need sorted. If child categories (terms) are defined, tose can be sorder too using the same interface?

Also you can have the admin terms interface sorted per your new sort.?

This plugin is developed by Nsp-Code

Should be;

Order Categories and all custom taxonomies terms (hierarchically) using a Drag and Drop Sortable javascript capability. No Theme update is required the code will change the query on the fly.?
If multiple taxonomies are created for a custom post type, a menu will allow to chose the one need to be sorted. If child categories (terms) are defined, those can be ordered too using the same interface?

Also you can have the admin terms interface sorted per your new sort.?

This plugin is developed by Nsp-Code

6. Misspelling of replced
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/taxonomy-terms-order/dev-readme/en-ca/default?filters%5Boriginal_id%5D=2916525
String – the_title filter replced with terms_walker
Should be – the_title filter replaced with terms_walker

7. Misspelling of textomain
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/taxonomy-terms-order/dev-readme/en-ca/default?filters%5Boriginal_id%5D=2916523
String – textomain folder fix
Should be – textdomain folder fix

8. Incorrect base local for localisation
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/taxonomy-terms-order/dev-readme/en-ca/default?filters%5Boriginal_id%5D=1344691
String – Localisation Implement, Dutch and Romanian.
Should be – Localization Implement, Dutch and Romanian.
*Localisation is the en_AU/en_GB spelling, all base strings should be in en_US.

Hope they all make sense, feel free to poke me when done and I’ll retranslate.

Cheers

Minor Spelling in Readme – becasue

Garrett Hyder — Wed, 10 May 2017 17:50:18 +0000

Hello,

Just wanted to flag a spelling issue in your Readme I came across while translating en_CA.

Permalink – https://translate.www.ads-software.com/projects/wp-plugins/better-wp-security/dev-readme/en-ca/default?filters%5Boriginal_id%5D=3571239
String – Enhancement: Added a note that the Filter Request Methods setting in System Tweaks should not be enabled if the WordPress REST API is used. This is becasue the DELETE HTTP method is blocked when the setting is enabled.
Word – becasue
Should be – because

Cheers

Translation Items

Garrett Hyder — Wed, 10 May 2017 17:14:36 +0000

Hello,

I was just running through your en_CA translation to bring it up to 100% and found a few minor items;

1. The wording and spacing seems awkward here;
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/charitable/dev/en-ca/default?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=3348483&filters%5Btranslation_id%5D=49056429
String;

To prepare for this update, you can?
→ → → → → → → → we strongly recommend creating a PayPal sandbox account and testing a donation in the sandbox using the form below.

*The sentence seems cut and doesn’t flow ‘To prepare for this update, you can…’ can what?

2. Broken link caused by newline
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/charitable/dev-readme/en-ca/default?filters%5Boriginal_id%5D=3873625
String;

Add a notice to the donation form when viewed by site admin to remind them that Test Mode is enabled. [#233](https://?
github.com/Charitable/Charitable/issues/233)

*The newline character breaks the URL, but also this is the only string using markdown for link rather than html, might want to switch to html for consistency.

Feel free to ping me if you make any string changes and I can retranslate.

Cheers

Spelling/Grammar – Minor Issues with Strings

Garrett Hyder — Tue, 11 Apr 2017 21:50:12 +0000

Hi Syam,

I’ve translated your plugin for en_CA and found two minor string issues listed below;

1. ‘allow’ should be ‘allows’
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/wpfront-user-role-editor/dev/en-ca/default?filters%5Boriginal_id%5D=932204
String – This screen allow you to restore WordPress built-in roles to its standard capability settings.
Should be – This screen allows you to restore WordPress built-in roles to its standard capability settings.

2. ‘capabilites’ should be ‘capabilities’
Permalink – https://translate.www.ads-software.com/projects/wp-plugins/wpfront-user-role-editor/dev/en-ca/default?filters%5Boriginal_id%5D=932039
String – %s to customize capabilites.
Should be – %s to customize capabilities.

You can update this ticket when updated and I’ll retranslate the updated strings.

Cheers