Skip to main content
Archived

Investigation and Enhancement on Internationalization of FME

Related products:Integrations
  • January 27, 2016
  • 0 replies
  • 11 views
takashi
Celebrity

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.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
    This post is closed to further activity.
    It may be an old question, an answered question, an implemented idea, or a notification-only post.
    Please check post dates before relying on any information in a question or answer.
    For follow-up or related questions, 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.

    Community Stats

    32,713
    Posts
    124,128
    Replies
    41,199
    Members
    Terms & ConditionsAccessibility statement
    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.