Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

Where is "Form locale" looked up from??

Avatar

Level 4

Hi,

In LC designer under form properties > Defaults you can set Locale. We use Viewer's system locale

Today all our forms have . (dot) and , (comma) mixed up in numeric fields.

- We have not changed the forms

- We have not changed/updated Acrobat/reader software or changed language from danish to english

We do not know if changes in windows have happend. Some GPO settings have been changed as Office 2007 have been lanched

Help is much appreciated and needed... I need bright input NOW

/Thomas

Jyske Bank, Denmark

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Locale definitions are also stored inside the XFA definition.  You can see them if you go into XML Source view and search for: "localeSet".

The localeset will embed the ambient locale of the form designer's system, and will also embed all locales referenced by the form.

So if you want to guarantee that the Danish locale gets embedded, then create at least one object on your form that explicitly uses that locale.

Also bear in mind that once a form with an ambient locale is opened and saved, the locale setting will be preserved in form state.

That way the form appearance will remain consistent if it gets sent to someone else who has a different ambient locale.

locale can also be explicitly set via script if need be.

  John

View solution in original post

4 Replies

Avatar

Level 10

Hi,

Have you looked in the Windows Control Panel; under Regional & Language Options you have two settings that may help:

Otherwise change the locale from viewer's settings to Danish (Denmark).

Hope you get it sorted,

N.

Avatar

Level 4

Hi niall

we have allready checked windows in that setting and it looks correct, with correct danish seperators

100.000,00 DKK  = correct

but still in our forms

100,000.00 DKK = WRONG

anyone other with ideas??

we think about hardcoding locale to danish. we have 500 pdf forms that need updated XDP and later saved to PDF

/Thomas

Avatar

Correct answer by
Former Community Member

Locale definitions are also stored inside the XFA definition.  You can see them if you go into XML Source view and search for: "localeSet".

The localeset will embed the ambient locale of the form designer's system, and will also embed all locales referenced by the form.

So if you want to guarantee that the Danish locale gets embedded, then create at least one object on your form that explicitly uses that locale.

Also bear in mind that once a form with an ambient locale is opened and saved, the locale setting will be preserved in form state.

That way the form appearance will remain consistent if it gets sent to someone else who has a different ambient locale.

locale can also be explicitly set via script if need be.

  John

Avatar

Level 4

Hi,

To correct our production problem, we set all forms to danish locale - earlier we use the 'ambient locale'. This made the correct seperators in amounts etc

Days later, our IT department found out, that the codepage had been changed by mistake. This was deeper in the Windows system, as windows regional settings still displayed danish. When corrected it solved the issue

/Thomas G
Jyske Bank.. soon going to MAX 2009

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----