CFONT - I18N:Cascading font

The following messages are stored in message class CFONT: I18N:Cascading font.
It is part of development package SPOOL_CASCADING_FONTS in software component BC-CCM-PRN. This development package consists of objects that can be grouped under "Cascading Fonts Configurator".
Message Nr
Message Text
001This cascading font for this Unicode area exists already.
002Please upload the corresponding true type font now.
003Cascading font cannot be created.
004Please select a line.
005Cascading font cannot be changed.
006Please select a line or lines.
007Action cancelled.
008Please input all necessary field(s).
009This Unicode area is not enabled yet.
010Please input a correct Unicode area. This area is not supported.
011The cascading font exists already.
012Please do not change the Sub SAP Font for 7-bit ASCII area.
013Please input a uploaded font.In menu bar, you can choose to upload fonts.
014Problem exists when finding jobs.
015Job already exists.
016Problem exists when opening jobs.
017Problem exists when closing jobs.
018Job scheduled.
019File name is too long.
020Undeleted font(s) is(are) still in usage,so it is not possible to delete.
021Error occured.
022Other Uncodeareas belonging to the same script are also added.
023No font is for the script,leave it empty,input Unicodefont in next field.
024One default Unicode font for this device type already exists.
025Please select a valid cascading sapfont name from the list.
026The default font can be only Unicode font.
027It is already default font.
028It is not applicable set Windows Unicode font as default font.
029The specified device type is not allowed and pls create it in TX SPAD.
030Please select only 'Z*' or 'Y*' device types.
031Data of table &1 has been initialized.
032Device type &1 cannot be built successfully(&2).
033Device type &1 has been built successfully.
034Font &1 cannot be uploaded successfully.
035Font &1 has been uploaded successfully.
036File &1 cannot be loaded successfully in report &2.
037FontInfo(e.g.char width) cannot be extracted from &1 in report &2.
038The settings of device type &1 have been deleted.
039The default font has been changed from font &1 to font &2.
040Font &1 has been deleted from table &2.
041Batch job will start, and pls access Goto/Main log to see the status.
042Updating Device type &1 is triggered.
043Please upload fonts first. In menu bar, choose 'Fonts/Upload fonts'.
044Font &1 has been deleted from cascading font list.
045Please make sure your fontinfo is from the uploaded configation file.
046The program cannot determine if device types are building in background.
047Device types are building in background, so data is in display mode.
048Device types are building in background,so device type cannot be deleted.
049Device types are building in background, so action cannot work.
050Please init the device type data with 'Full settings' mode.
051Only one fallback Unicode font is allowed per cascading font for PCL.
052Building dev.type &1 trace: &2.
053The program always set 'Same FontFile for all vars' on for Unicode fonts.
054It is not applicable to set it for Windows device types.
055It is unable to open the file dialog.
056Please input a correct file name.
057Please be sure that the file is with '.xml' extention.
058The settings have been downloaded correctly.
059The settings cannot been downloaded correctly.
060The settings cannot be uploaded.
061The settings have been uploaded correctly.
062No Unicode Fonts are uploaded.
063A font for ABAPList is ABAPL_*. * is lang info(Table t002:Field LAISO).
064The device type exists already.
065You didnot specify 'Courier' to Arabic,this may cause formatting problem.
066Since global settings are empty, it is set according to the device type.
067Dev.type &1 has different SAPFONTNAME for &2,&3 from global settings.
068Table entries are recorded in the request.Pls check it before release it.
069Fontname and Fontinfo should be equal in one row of a SAPWIN device type.
070No font info is wrong.
071The font info for the following script(s) is wrong: &1 .
Privacy Policy