Optimization of using text constants

Question

Does Forms compiler optimize using text constants when it make *.fmx
file, if yes then how?
What I mean. In many cases Forms programmers use text constants to do
any actions, for sample:
- do_key('EXECUTE_QUERY');
- if (:system.mode = 'ENTER-QUERY') then /* ... */ end if;
- execute_trigger('ON-POPULATE-DETAILS');
- show_alert('ASK_SAVE');
- go_block('ORDERS') or go_item('ORDERS.NAME');
- set_block_property(bid,DEFAULT_WHERE,':orders.pay > '||:r.pay_rate);
As I have undestood myself, Forms divide such constant on types:
- standart text constants('EXECUTE_QUERY','ENTER-QUERY' ...);
- user's text constants ('ASK_SAVE','ORDERS.NAME');
And Forms do any optimization with standart text constants: in *.fmx file
I found only one enter for every from such constants.
But for user's text constants Forms does not optimization: in *.fmx file
I found more then one enter for such constants.
If above is right then is there benefit from creating a package in form
module and creating constants in the package, that contain frequently used
user's text constants(block and items names, e.t.c.) and then writing down
in program these package constants instead of user's text constants?

Answer 1

I get to answer my own question. I found a workaround should you ever what to be sure a certain font is used and not replaced. Granted, this will add my download time but you at least can preserve the look.
Simply make any text with a shadow. But make the offset 0 and the transparency to 1 (you can't make it 0). You won't even notice the "shafow" and the text will be made into a graphic every time.
Stephen