Webtags/Parameters (preserving history): Difference between revisions

Webtags/Parameters (preserving history) (view source)

Revision as of 19:01, 23 July 2021

123 bytes added , 19:01, 23 July 2021

m

→‎Migrating from legacy to MX: simplified

Sfws

5,838

edits

@@ Line 722: / Line 722: @@
-== Migrating  from legacy to MX==
+== Migrating from legacy Cumulus 1 to MX==
-If you use NOAA type report functionality, and choose to transfer your existing [[Cumulus.ini (Cumulus 1)|existing configuration file (cumulus.ini)]] to [[Cumulus.ini|MX]], you need to be concerned about how to represent a month.
+If you have created any legacy cumulus template files, then in each template, you will need to do some editing. Everywhere a web tag appears with an output modifiers that is used to specify a date and/or time format, has to be edited before that template will work for MX.
-If you have created any Cumulus template files, then every place in each template, where an output modifiers is used to specify a date and/or time format, has to be edited. For web tags it is much more complicated, simply because it is not just month we may be representing, and we might require only one specifier (being careful whether we use a standard or custom modifier) or we might want to specify a combination of modifiers (and we might want to add a space character or other literals). It is difficult to summarise, but here are some potential issues:
+Here are the main reasons:
 * the reserved characters are different in C1 and MX (affecting use of literals like "on" and "at" that appear in many English time-stamps)
+* the Delphi in legacy Cumulus is case insensitive, so for example "H" and "h" have the same meaning
+* MX is case sensitive, and symbols mostly have different meanings when one symbol is used to when that symbol is used with others, so for example "H" and "h" have different meanings, and if not used with other symbols will need to be preceded with a "%" to have same meaning as they have in combination with other symbols
+* In the legacy cumulus, a symbol like "d" has the same meaning for any tag
+* MX is inconsistent, a symbol like "d" changes its meaning depending on the tag it is used with (e.g. the script conditional ''''<#metdateyesterday format=d>' == '<#yesterday format=d)>''''  will never be equal as the LHS returns a full date and the right hand side returns day of month only)
+* the symbols used for representing such modifiers as minutes, month, am/pm, are different between C1 and MX.
 * MX introduces the concept of escaping characters (a '''\''' placed before a character can be either a control sequence or an instruction to display the character)
-* MX is inconsistent e.g. '''format=d''' gives a different result depending on the tag it is applied to (e.g. the script conditional ''''<#metdateyesterday format=d>' == '<#yesterday format=d)>''''  will never be equal as the LHS returns a full date and the right hand side returns day of month only)
+* In the legacy Cumulus, a space is a gap between characters
-* in MX space in some cases may need to be within the single quotes containing other literals (as in MX space can change the interpretation of a modifier character).
+* In MX, a space must be within a literal, as a space before a symbol has the same effect as "%", (it changes the interpretation of a modifier character).
-'''Confused even more now?''' I'm not surprised, but maybe some examples will help before we actually list the available modifiers.
+'''Confused even more now?''' I'm not surprised, but maybe some examples will help.
 === Examples ===
@@ Line 755: / Line 760: @@
 ** but alternatively you can escape each verbatim character with a backslash as prefix (Cumulus MX).
 * You may need to use both single quotes and back slashes in some format specifiers, depending whether the characters you want to include can be interpreted as control characters (yes, backslash is also used to escape control characters, so backslash will NOT work for some characters such as those in "on" and "at" [\n will produce new line not the letter n, \t will produce a tab not the letter t]), consequently for some characters you must use the literal approach to include them in your format.
 == Past history for this page==