Skip to main content

We where using  TRANSLATE-TO-ANSI                1

 

Since we move to 10.1 we try to used
  COBOL-CHARACTER-SET              ANSI

 

It is not working!

We where using  TRANSLATE-TO-ANSI                1

 

Since we move to 10.1 we try to used
  COBOL-CHARACTER-SET              ANSI

 

It is not working!

Have you tried COBOL-CHARACTER-SET 437 or the value of the current code page. I reproduced the issue of setting COBOL-CHARACTER-SET  ANSI  I was able to get my program working when I used COBOL-CHARACTER-SET 437. I submitted the COBOL-CHARACTER-SET  ANSI issue to Development.


We where using  TRANSLATE-TO-ANSI                1

 

Since we move to 10.1 we try to used
  COBOL-CHARACTER-SET              ANSI

 

It is not working!

I have another problem with this...

when Umlauts are used hardcoded it is strange.

          03  haupt-screen, visible is haupt-visible.

              05  label "PROGRAMMAUSWAHL", foreground-color = 4

                  line 1, col 30, font big-font, size 30.

              05  label "01  Angebot erfassen"

                  line 3,5, col 30 font p-font.

              05  label "02  Angebot ändern"

                  line 5, col 30 font p-font.

              05  label "03  Angebote suchen"

                  line 8,5, col 30 font p-font.

              05  label "10  Angebote mit Artikel X ermitteln"

                  line 12, col 30 font p-font.

              05  label "99  Ang. Email-Log"

                  line 20, col 30 font p-font.

          03  entsch-screen, visible is entsch-visible.

              05  label "GENERALENTSCHEID", foreground-color = 4

                  line 1, col 30, font big-font, size 30.

              05  label, value lnk-nr, line 1, col 100,

                  pic z(4)9, font p-font.

              05  label "01  Angebot versenden"

                  line 3,5, col 30 font p-font.

              05  label "02  Versand-/Konditionenübersicht"

                  line 5, col 30 font p-font.

              05  label "03  Ändern Angebotskopf"

                  line 8,5, col 30 font p-font.

              05  label "04  Ändern Angebotspositionen"

                  line 10, col 30 font p-font.

              05  label "05  Kalkulationsübersicht"

                  line 11,5, col 30 font p-font.

              05  label "06  Positionen kopieren"

                  line 15, col 30 font p-font.

              05  label "09  Objektbericht"

                  line 18,5, col 30 font p-font.

 

the lines with "ä" are displayed but when a "ü" is inside a the part behind the number is cut away.


We where using  TRANSLATE-TO-ANSI                1

 

Since we move to 10.1 we try to used
  COBOL-CHARACTER-SET              ANSI

 

It is not working!

Sasdly, I do not reproduce this. In your screen shots, I don't see Versand-/Konditionenübersicht displayed on the GENERALENTSCHEID screen. That seems odd as there isn't a "ä" or "ü" in that label. I do not see that the numbers in GENERALENTSCHEID screen are truncated. With 10.1 we provided some Unicode abilities, oerhaps the number being cut away is due to a difference in 10.1.0 - When a control is sized based on the size of the font used, it could be a different size than in previous versions. This difference is remedied by ECN-4468.

We where using  TRANSLATE-TO-ANSI                1

 

Since we move to 10.1 we try to used
  COBOL-CHARACTER-SET              ANSI

 

It is not working!

when i write instead the "ü" a "ue" which needs more space it is visible.
I changed it to "ö" it is visible..

Hardcoded ü in a grid and so on works. Stored "ü" which get displayed over labels also works.
Umlauts in Window-Titles don't works.

When i modify the Umlauts in Titles to another codepage then it gets displayed correct. So the codepage in Titles seems to be always the default-value from COBOL-CHARACTER-SET

We where using  TRANSLATE-TO-ANSI                1

 

Since we move to 10.1 we try to used
  COBOL-CHARACTER-SET              ANSI

 

It is not working!

Please send in an example to Customer Care so we can take a look into this. Thanks.