Learning to layout simple code ?

Having come into EMC from superCam/Turbo cam, I feel I have a basic understanding of Gcode instructions, and having managed to write some simple projects for them and cut successfully,
I'm a bit thwarted by the code I find in the axis.ngc file.
Working in XP, I've now got Taskpad as a text editor, and can start to learn more, as I examine that code to carve "AXIS EMC2".
What has thrown me somewhat, is the "syntax"(?).
I don't know if that's the right word, but what I mean is that although each Gcode is easily found in the manuals, and I'm aware of things like parameters, and such like, but I can't find a reference to "how to write code for EMC2", the nitty gritty of laying it out.
I'm not thinking of writing out huge blocks of code, merely small jobs, or modifications to existing files.
For example, it would be fun to modify the lines of code so that the m/c would carve "AXIS E=MC2".
Can someone point me to any such help ?
Much appreciated,
John

Thanks John.
I've started the long learning curve, and a book to lean against the coffee pot would help, so I often print manuals out, just to avoid the glare of the laptop.
SWMBO reckons I get square pink eyes
It's the variation in "style" or layout that I need to get into my head, I think.
I've got an overall grasp of it, just trip over the details

John

I've started to read the article at www.isd.mel.nist.gov on RS274/NGC language, and noticed their use of the word "dialect" for the Gcode that is used by EMC, so perhaps that's the best I can do at the moment.
But I'll put my thinking cap on, and try and come up with a fuller explanation asap.
John

EDIT It may be just that I started at the deep end, so I've gone back to read the gcode overview in the User manual, and try to get a grip there.
I have spotted one difference - my previous but short experience was with 247D, and I didn't come across the use of <> signs.
But then I didn't come across a lot else, so it may just be a spot of indegestion that's stopping me running before I can walk.

Notes so far - There are certainly more functions available, and using slightly different names, like ASIN instead of ARCSIN, the use of ** instead of ^ for "raise to the power of".
But perhaps more importantly, in Chapter 9, the order of execution defined by a list rather than by position in the line.
Happily, Chapter 10 suggests that it is more important to write unambiguous code than follow chapter 9.
So I think I shall make out now.
John

As a precursor to writing the code, and to save me a lot of typing, does anyone know of a piece of software that will convert a simple vector drawing into an xy data set ?
I've got a ancient digitizer pad, and could draw over a printout of the drawing, but it ought to be much quicker, and more accurate "on screen".
I've tried googling every combination of words that might point me to one, but I generally get something far to complex that will take me longer to learn than to do it the slow way.
John