Microsoft/alguidelines
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

deploy: 2d3e5d02a2

Browse source
This commit is contained in:
JeremyVyska 2021-11-10 09:17:12 +00:00
parent 27483c8f45
commit 740dbf4e5a
149 changed files with 3229 additions and 2860 deletions
Download patch file Download diff file Expand all files Collapse all files

10
navpatterns/3-cal-coding-guidelines/localizability/index.xml
View file

@ -1,18 +1,18 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Localizability on BC AL Help</title><link>https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/</link><description>Recent content in Localizability on BC AL Help</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/index.xml" rel="self" type="application/rss+xml"/><item><title>CaptionML on System Pages</title><link>https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/captionml-for-system-tables/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/captionml-for-system-tables/</guid><description>CaptionML should always be specified on a page field for a system table. By default, system tables do not have captions, so if you need to use them in the UI then captions need to be added.
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Localizability on AL Guidelines</title><link>https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/</link><description>Recent content in Localizability on AL Guidelines</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/index.xml" rel="self" type="application/rss+xml"/><item><title>CaptionML on System Pages</title><link>https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/captionml-for-system-tables/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/captionml-for-system-tables/</guid><description>CaptionML should always be specified on a page field for a system table. By default, system tables do not have captions, so if you need to use them in the UI then captions need to be added.
Bad code
... { 2 ;2 ;Field ; SourceExpr=Name } ... OBJECT Table 2000000000 User ... { 2 ; ;Name ;Text50 } Good code
... { 2 ;2 ;Field ; CaptionML=ENU=Name; SourceExpr=Name } .</description></item><item><title>FIELDCAPTION and TABLECAPTION</title><link>https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/fieldcaption-and-tablecaption/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/fieldcaption-and-tablecaption/</guid><description>For user messages, errors etc., use FIELDCAPTION not FIELDNAME and TABLECAPTION not TABLENAME.
... { 2 ;2 ;Field ; CaptionML=ENU=Name; SourceExpr=Name } .</description></item><item><title>FIELDCAPTION and TABLECAPTION</title><link>https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/fieldcaption-and-tablecaption/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/fieldcaption-and-tablecaption/</guid><description>For user messages, errors etc., use FIELDCAPTION not FIELDNAME and TABLECAPTION not TABLENAME.
Reason:
The correct translation will be automatically used. If the caption/name changes, then there will be a single point of change needed. Bad code
IF NOT CONFIRM(UpdateLocationQst,TRUE,FIELDNAME(&amp;quot;Location Code&amp;quot;),...) Good code
IF NOT CONFIRM(UpdateLocationQst,TRUE,FIELDCAPTION(&amp;quot;Location Code&amp;quot;),...)</description></item><item><title>Global Text Constants</title><link>https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/global-text-constants/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/global-text-constants/</guid><description>Declare Text Constant as global variables.
IF NOT CONFIRM(UpdateLocationQst,TRUE,FIELDCAPTION(&amp;quot;Location Code&amp;quot;),...)</description></item><item><title>Global Text Constants</title><link>https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/global-text-constants/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/global-text-constants/</guid><description>Declare Text Constant as global variables.
Bad code
PROCEDURE GetRequirementText@6(...) : Text\[50\]; VAR RequirementOptionsTxt@1002 : TextConst 'ENU=Shipment,Receive,Pick,Put-Away'; BEGIN Good code
VAR RequirementOptionsTxt@1002 : TextConst 'ENU=Shipment,Receive,Pick,Put-Away'; ... PROCEDURE GetRequirementText@6(...) : Text\[50\]; BEGIN</description></item><item><title>Use Text Constants</title><link>https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/use-text-constants/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/use-text-constants/</guid><description>Pass user messages using Text Constants. It makes translation easy.
VAR RequirementOptionsTxt@1002 : TextConst 'ENU=Shipment,Receive,Pick,Put-Away'; ... PROCEDURE GetRequirementText@6(...) : Text\[50\]; BEGIN</description></item><item><title>Use Text Constants</title><link>https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/use-text-constants/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/use-text-constants/</guid><description>Pass user messages using Text Constants. It makes translation easy.
Bad code
ImportAttachmentQst@1021 : TextConst 'ENU=&amp;quot;Import attachment &amp;quot;'; ... IF CONFIRM(ImportAttachmentQst + Caption +'?',TRUE) THEN BEGIN Good code
ImportAttachmentQst@1021 : TextConst 'ENU=&amp;quot;Import attachment %1?&amp;quot;'; ... IF CONFIRM(STRSUBSTNO(ImportAttachmentQst, Caption),TRUE) THEN BEGIN Bad code
... IF NOT CONFIRM( STRSUBSTNO( 'Difference on Periodic entries: %1 on %2' + 'Do you want to continue?',Balance,Date), TRUE) THEN ERROR('Program terminated by the user'); Good code</description></item><item><title>Using OptionCaptionML</title><link>https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/using-optioncaptionml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://bcalhelp.dev/navpatterns/3-cal-coding-guidelines/localizability/using-optioncaptionml/</guid><description>The OptionCaptionML should be filled in for sourceexpression using option data types.
... IF NOT CONFIRM( STRSUBSTNO( 'Difference on Periodic entries: %1 on %2' + 'Do you want to continue?',Balance,Date), TRUE) THEN ERROR('Program terminated by the user'); Good code</description></item><item><title>Using OptionCaptionML</title><link>https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/using-optioncaptionml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/localizability/using-optioncaptionml/</guid><description>The OptionCaptionML should be filled in for sourceexpression using option data types.
Bad code
{ 30 ;TextBox ;17850;0 ;150 ;423 ;Name=Selection; SourceExpr=Selection; DataSetFieldName=Selection } ... Selection@1008 : 'Open,Closed,Open and Closed'; ... Good code
{ 30 ;TextBox ;17850;0 ;150 ;423 ;Name=Selection; OptionCaptionML=ENU=Open,Closed,Open and Closed; SourceExpr=Selection; DataSetFieldName=Selection } ... Selection@1008 : 'Open,Closed,Open and Closed';</description></item></channel></rss>