Skip to main content
Archived

Investigation and Enhancement on Internationalization of FME

Related products:Integrations
crutledge
  • crutledge
    crutledge
takashi
Influencer

Actually FME 2016 is not friendly to non-ascii characters. I encountered several cases where Japanese characters (within file/folder paths, attribute names etc.) causes unexpected behavior.The situation is worse than 2015. I'm afraid that more hidden problems exist yet.

Similar issues probably occur in other non-ascii locales. I strongly hope thorough investigation and enhancement regarding FME i18n will be done.

    This post is closed to further activity.
    It may be a question with a best answer, an implemented idea, or just a post needing no comment.
    If you have a follow-up or related question, please post a new question or idea.
    If there is a genuine update to be made, please contact us and request that the post is reopened.

    Helpful Members This Week

    Community Stats

    31,353
    Posts
    118,929
    Replies
    38,971
    Members

    Latest FME

    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.