It should be possible to configure fee for Cash on Delivery usage.

Consider possibility to use MSP CacheOnDelivery module as a solution.

Move https://github.com/Magento-Japan/m2-jplocalize/tree/master/region to magento/magento2-jp

Utilize extension points developed in #16 and provide handler for Japanese zip address

Magento 2 now have several places where customer full name is formatted. This lead to code duplication and completes customizations that is required to apply formats specific to locales. In the scope of this issue new API service should be introduced that will return customer full name based on customer data (last name, firstname etc.)

Service should be declared as an interface and has default implementation equal to current behavior.

Magento should correctly handle JPY currency.

Note: implementation for MVP may assume that JPY is only currency used in Magento.

The initial implementation is in https://github.com/magento/magento2-jp/tree/2.3-develop/Price. Please also consider that all fixes from https://github.com/magento/magento2-l10n/2 taken into account.

After Magento2.3.2, CheckoutAddressSearch was added into Magento core implementation. This is good new feature for B2B and Gift usage.
However this new module brought new knockout templates and ui components.

Above screenshot has wrong address format on checkout address search result list.
This should be same as right navigation.

Also shipping / billing selected address format are not correct.

Update JP regions to utilize mechanism introduced in magento/magento-jp#20. Optionally migrate to declarative schema

All PRs to magento/magento2-jp should be verified with a Travis CI on latest magento/magento2 code (2.3-develop branch)

To speed up a process git may clone only latest code

clone -b 2.3-develop --single-branch --depth 1 [email protected]:magento/magento2.git

When zip code is entered all possible address fields should be updated automatically.

Initial implementation in https://github.com/magento/magento2-jp/tree/2.3-develop/Zip2address

Magento should correctly handle currencies without subunits, including JPY.

As tasks actual not only for Japanese yen solution should be implemented in magento/magento2-l10n repository (or in magento/magento2).

This epic includs researching and fixing all places in Magento 2 Open Source with incorrect handling of currency subunits and assumption that for currency valid expression superuints/subunits = 100.

Provide an implementation of name formatter developed in #22 to select one of existing locale-specific implementation (e.g. #24) based on store view locale

Move https://github.com/Veriteworks/Zip2Address to magento/magento2-jp

Magento 2 always sort regions alphabetically. For some regions it is not suitable solution or merchant may want to adjust sort order if it operates mostly in some specific areas. Magento core should provide a possibility to specify weights/sorting priority for regions

PDF files generator should use multibyte fonts with the support of Japanese characters.

Hello,

Catalog price with comma is rounded to 1 digit number as the comma " , " is converted to the decimal point " . " automatically.

example:
3,700 > 3.700 > 4

If the price is saved without comma, the correct price is stored with comma, though.

example
3700 > 3,700

Any suggestions will be really appreciated.

Best,

Move https://github.com/Veriteworks/StoreAddress to magento/magento2-jp

Some files contain @codingStandardsIgnoreFile annotation, which stops static tests from being effective.

Annotation should be removed and files refactored to comply with the existing coding standards.

Based on solution implemented in #18 register Kuromoji as desired analyzer/tokenyzer for Japanese stores

Perfectures (regions) should be added to the directory and listed in order from North to South.

Initial implementation is in https://github.com/magento/magento2-jp/tree/2.3-develop/Region

Hello,

Just installed yesterday. Working very charm. Really wonderful experience.

I'm not sure this is temporary issue or not, the order of Kana form on checkout page, Family name's furigana and First name's furigana, they are now reverse. I think, at least, the current ordering is not so natural.
Please kindly see the below images.

How to change the ordering of the shipping address kana form on checkout page?

Best,

ElasticSearch indexes should be configured properly with kuromoji analyzer/tokenizer.

Initial implementation https://github.com/magento/magento2-jp/tree/2.3-develop/Kuromoji. Please also align with https://github.com/magento/magento2-l10n/pull/1 to not miss parts that should b emodified.

Some local markets expect that Magento will be configured in some particular way. To simplify locale-specific configuration Magento 2 may introduce some configuration presets.

User scenario:

1. Admin change a locale
2. System shows him actual and recommended a configuration for selected locale.
3. Admin able to modify nothing/all/only some configuration options at once

STR:

1. Open Magento Admin
2. Go to product add page
3. Fill product information with Japanese or another double byte characters (e.g. Chinese, Hindy, etc.)

ER: URL key automatically generated

AR: URL key is empty

4. Click New Category button
5. Fill data
6. Save change

ER: request processed succesfully
AR: error message displayed

Provide Japanese specific name format with Kana

Move https://github.com/Veriteworks/kuromoji to magento/magento2-jp

Sometimes Japanese merchants cannot read English.
Even though TinyMCE has easy to understand interface, some of them hope to change its interface into Japanese.

In all places, name should be formatted to LastName FirstName OptionalPolitnessSuffix.

Please consider all placed modified in https://github.com/magento/magento2-l10n/pull/3.

Implement Store Address template in magento/magento2-l10n.

Move existing code developed by Veriteworks Inc. to magento/magento2-jp repository

1. Modules should be modified to use MagentoJapan namespace
2. Directories structure should use following rule:

<repo_root>/
           <Module1>
                Test/
                    Unit/
                    Integration/
                    Mftf/
                               TestSuite/
                               composer.json
           <Module2>
           <Module1SampleData>
           <Module2SampleData>

It is a common task to fill region, province, city or street by zip code or suggest zip code based on the already available information. Magento core should provide set of handlers to implement region-specific implementation easier.

Core should include:

1. Listener of zip code field change that will send changed value to registered handler(s). Hendler(s) will return array of fields that may be automatically filled. Implementation of concrete handler is a responsibility of separate modules
2. Possibility to register handler that will return list of possible zip code based on available address data. Implementation of concrete handler is a responsibility of separate modules

Should be possible to configure store address from Admin Panel.

Initial implementation at https://github.com/magento/magento2-jp/tree/2.3-develop/StoreAddress

During installation of Magento Japanese Localization default options should automatically apply (e.g. locale code, currency code, measurement units, etc.)

Add katakana fields to the customer account and address forms.

Initial implementation provided in https://github.com/magento/magento2-jp/tree/2.3-develop/Kana

Provide possibility to specify desired delivery date and time.

Refactor code to utilize unified customer full name formater developed in #22

In Japan email address not corresponding to ISO are widely used. As they are not valid from the standard point of view Magento does not accept them. Core should provide possibility to disable this check. The same issue with recently added top level domains (e.g. magento/magento2#11945 and magento/magento2#11689).

On of possible approach is to provide a configuration option to admin that will allow "soft email validation" which will validate that email has format <username with any characters except @>@<domain with any characters except @>. By default this option should be disabled so behaviour will remain the same.

Magento 2 has hardcoded Elasticsearch analyzer/tokenyzer. Existing implementation should be extended to provide a possibility to change analyzer/tokenyzer. At primitive implementation, it may be argument passed by DI. Also possible implementation is to provide possibility to choose analyzer/tokenyze from admin config panel per store view. More suitable solution will be to pick correct analyzer/tokenyzer based on store locale and provide possibility to other modules register their implementation of choosing valid analyzer/tokenyzer.

Any of listed solution is valid and it is up to developer which path to follow.

Some places in Magento has hard-coded dates format that ignores store locale or locale of admin panel. All dates displayed on the client side should be formatted according to selected locale. This epic is created to hold issues reports for each particular case to fix.

Move https://github.com/Magento-Japan/m2-jplocalize/tree/master/kana to magento/magento2-jp reposiotry

Japanese localization should contain translations for all Magento Open Source phrases and all phrases for modules included in localization.

Translation package should be included in the same repository as localization modules and available with composer and git-based installations.

As the source of translation phrases please use https://crowdin.com/project/magento-2/ja

Utilze extension point developed in #13 to provide Japanese specific store address template

Hello,

Customer registration form is not available when click [Create an Account / Sign Up] button on Thank you page after placing order.

On Chrome and Firefox.

Any suggestions will be really appreciated.

Best,

Hi, there,
I have been enabled these modules.

• Magento_CurrencyPrecision
• Magento_JapaneseAddress
• Magento_JapaneseDefaultConfig │
• Magento_JapaneseDefaultCmsPages │
• Magento_JapaneseName │
• Magento_JapanesePostalCode │
• Magento_JapaneseRegion │
• Magento_JapaneseStoreAddress │
• Magento_JapaneseYenFormatting

After enabled modules, It show below log.
Plugin class Magento\JapaneseAddress\Plugin\Customer\Model\Name doesn't exist main.CRITICAL: Plugin class Magento\CurrencyPrecision\Plugin\Directory\Model\CurrencyPrecisionFormatting doesn't exist [] [] main.CRITICAL: Plugin class Magento\JapaneseName\Plugin\Framework\Data\ExtensionAttributesValues doesn't exist [] [] Plugin class Magento\CurrencyPrecision\Plugin\Directory\Model\CurrencyPrecisionFormatting doesn't exist

Environment
・magento 2.3.0(update from 2.2.7 by composer)
・php7.2 + nginx + varnish

Please tell me what should I do.
Thank you

Create Composer meta-package to be able install all Japanese localization modules by single Composer require command.

Every included template should be verified for correct escaping of values. Following search patterns may be used: <?= <?php echo, echo, @escapeNotVerified