Two issues in Japanese Translation results RRS feed

  • Question

  • Hi,

    Extra space added:

    JP should not use a single space between single byte and double byte but the MSFT uses a space between those words.

    The red square is unnecessary space in JP.

    English Source texts for your reference:

     - How to size the solution to fit the customer's needs using the EMC VSPEX Sizing Tool or the Customer Sizing Worksheet

    - How to implement, with best practices, the resources necessary to deploy an end-user computing solution for View using VSPEX BLUE

    Wrong symblos used:

    JP should use double byte for symbols such as “ ”, “”, “”, “ ”..etc except for command or the segments which is left as English. MSFT uses single byte for those symbols.

    The red square should be double byte in JP  *no need to single space before “” and after “” if the word before “” and after “” are double byte.

    English source texts for your reference:

    - If you choose Network File System (NFS) as the cloud provider, ensure that the root level of the export is read-writeable (chmod 777 permission).

    Could you please take a look at the issues?





    Monday, September 7, 2015 10:29 AM

All replies

  • Hi Lynn,

    while not following the standard, we see that in publication practice there is often a space between Latin and non-Latin characters. We consider it safer to err on the side of maintaining the space in the Translator output.

    A single-width space is usually sufficient to denote the space, and in most instances aesthetically more pleasing.

    Thanks much for asking about this,
    Chris Wendt
    Microsoft Translator

    Wednesday, September 9, 2015 4:48 PM