Final Font

As you can see this is final edited version of my font. Looks a lot better.

Anyway, there are several changes I've made frim the initial testing of Pixel V2.

l Opted for a sans-serif font. Lends itself to the style I chose a over serif font. It's also a lot easier on the eye.

l Mixed alterations from revised characters of artefact 4 (the characters k, w, i.). They're now more in keeping with the overal style.

l Re-designed some upper-case such as the M, W and N

l Manually edited character width in fontlab, I realised that some of the upper-case characters were too wide, and that's why they looked odd. Many of the upper-case characters have had their overall width reduced to be more in keeping with the lower-case.

l Proper kerning implemented, upper-case, lower-case and punctuation glyphs. There are standardized gaps between the letters now. Flat edges have a gap of 35upm, rounded edges have 30upm. The lower-case r, f and t are the only exceptions because of their unique shape.

l Reduced stroke 0.5mm in Illustrator. Stroke width now 2.5mm. While the thinner stroke width does hinder readability, it's a non-issue as most of the characters are now clearer and easier to recognise.

l Reduced Caps-height as well as lowered any horizontal strokes for upper-case to sit above the x-height for added consistency. Now the Upper-case doesn't jump about all over the place. I think the font looks better for it.

• There is also the added thickness to the x and v characters so now they appear the same width as the other characters.
• Additionally the dots above the i and j characters have been raised to become more distinguished. They now sit half way between the x-height and the ascender.
• Re-designed lower-case r, w as well as made alterations to lower-case f.

 

5th Artefact - Questionnaire

Questionnaire Results

 As you can see, the majority chose Sans-serif as their preferred font, at both sizes. The results from question 2 and question 5 indicate that it is easier to read that the serif font, so in that case my final font will be a sans-serif font. Which to be honest, I think fits the overal style of the font much better than a serif font does.

Additionally, it's also overwhelmingly apparant that there is a noticeable difference between the two, despite the difference only being minor. I included that question to make sure that there was no confusion, and people could differentiate between the two.

Finally, there were several issues that question 7 brought to light.

The main concern being that the x and v characters look thinner than the other characters, despite being the same width in Illustrator. It's clear that I must make them thicker to compensate for the angle of the stroke.

Secondly, some participants expressed difficulty in reading the font as it appeared some letters were conjoined, a kerning issue. Something that I will address in my final font and make sure that the letters do not conjoin.

Finally

Client Project - Update 3

So here is what my homepage currently looks like. As you can see, it's not exactly how I initially designed it, and there is a good reason for this.

I've decided that given the timescale I have to build the other pages as well as the flash that needs to be embedded and coded, that it would be a better idea to produce a basic version of each element beforehand that focuses on function rather than appearance.

So far I've implemented the basic flash banner that sits below the navigation. I spent a long time messing around with many tutorials that either didn't work or were for AS2 instead of AS3. In the end I opted to not use Actionscript as that would only be required for a banner that has the option of the user choosing which picture they like, the basic version being just some images and some simple fades. I think still works just as well, however it is obviously less difficult to make and that therefore mean less credit, so I think once I have built the basic version of the site, this will be first element that I will advance.

I've also added a basic twitter feed which I also had to spend a lot of time fixing. After following a tutorial that ultimately ended up working, except for problem:

The feed is made up of three images. The top image, which includes the ''Recent Tweets'' header and the top of the speech bubble, a middle image of a 1px strip that is repeated as to accomodate any size tweet and a bottom image that comprises of the bottom of the speech bubble. Because of some formattig issues with the margins, this error occured. Although after much searching, I found the code to recitify this problem and close the gap.

''* {
                 margin: 0;
                   padding: 0;
  } ''

By placing this code at the top of my css document, the formatting was reset to default.

Apart from the usual issues with wrappers and positioning that css seems to bring, there have been few other problems and progress has been relatively smooth apart from the banner issue and the margin issue.


I had to make some changes to the design to accomodate users that may not have a wide/larger resolution. Initially I planned to have the dirt background for banner extend across the users screen, no matter what resolution. The same would have applied for the navbar. I decided against this for a few reasons:

1. Users with a wider resolution may suffer from longer loading times due the fact that they would be required to download a larger image for the dirt background. Obviously this affects accessibility as research has shown that websites with slower load times are generally less likely to hold the users attention. 
2. Another problem for users with wide resolutions is that the logos on the right-hand side of the navigation as well as the size alteration buttons on the opposite side, would leave large empty spaces either side of the content, making the website looking incomplete and unprofessional. 
3. I opted for a recent tweets as opposed to recent news. Again, this is the more basic element of an original piece of php. It does have it's benefits, one being that it's more secure as the login is based on a server with tighter coding (twiiter.com), it hold greater aesthetic value and also that it requires less coding for effectively the same effect. However, only one tweet can be shown at any given time, to view other tweets the user would have to click the hyperlink embedded within the recent tweets element.
   

I have also decided that an rss feed would be quite useless, as rss feed generally are used for websites that contain topical information. Many rss feeds that I have looked at on a range of websites encorporate links to other pages that feature related information or an article. While this could incorporated, I don't believe it's 100% neccessary. When I finally go to take pictures of the farm itself I will ask their opinion whether or not it would something they would have interested in/found useful. 

Currently, as the basic version goes, the rss will not be featured. 

Things to do:

• Gather content for other pages.
• Build Recent Events element, footer and text size alteration feature.
• Modify dirt background to emulate developed design.
• Code flash image gallery 

UPDATE:

I've inserted the text size alteration buttons, but am having trouble actually getting it to work. It could be a number of things. 

 I think It may have something to do with the banner, as the code is all correct and works in it's own document. The <script src> isn't meant to be there for text size alteration. It should  just be <script type='text/javascript>. To try and amend this I will duplicate index.html and remove the banner from one of the copies and alter the script and see if that makes a difference.

It could also be because the text itself isn't within the same wrapper as the javascript. I'm not sure how to get around this as usually the javascript is contained within the <head> tags, as opposed to the <body> along with all the other <divs>. As you can see, the bit highlighted in red is the corresponding tag given to the text to associate with the javascript. However this doesn't work.

I've also inserted the footer and some basic images for the recent events that will take the use to the events page. This took a lot longer than I anticipated, mainly because of formatting issues with the whole website being 200px to right for some reason, apparently it was something to do with the way I had coded the navigation. Initially the fb and twitter logos were in there own div which was wrapped in the navigation div, which was wrapped in a header gif to hold it all together. I removed the fb and twitter divs as well as the header which just left me with a navigation wrapper that is 1024px wide. I then had to insert two buffers either side of the linked pictures to make sure it all adds up and everything is where it should be. 

UPDATE 2: Text size alteration and the banner now work without conflict. Turns out that all I needed to do was insert the javascript just above the <p id='content'>. I initially feared that I could not have both as I moved the <script src='Scripts/AC_RunActiveContent.js" to within the <imagescroller> id and the size alteration worked, but the banner did not. 

That's all fixed now. One thing I should mention, is that instead of increasing the text size to set amounts (i.e. 12px, 18px, 22px and so on) the script simply multiplies the size by 0.2 or vice versa each time a button clicked. This allows for greater flexibility as the set sizes may not accomodate everyone and faster loads times thank to the reduced amount of code required. Here's a screenshot of it in action:

Text size after 2 clicks from default.

Text size after 4 clicks from default.


So as you can see it works well, there is one small snag though. After increasing the text 4 times the entire wrapper shifts around 5-10px to the right, but doesn't move again no matter how much the text is increased. I have no idea what causes this and if I have time i'll fix it. However it's not the biggest priority.

3rd Artefact - Sans Serif Font - Evaluation

3rd Artefact Evaluation

(I originally did this font before easter, but since I can't upload it to the uni servers. I'm writing the evaluation now in preparation to upload it tomorrow. )

I personally think that this design is the weaker between the Sans-serif version and the Serif version. I don't believe the Sans-serif version looks as appealing and the serif version. Why this is I'm not sure, although I think It may have something to do with the adjusted widths and stroke lengths. 

This artefact has the unaltered stroke length. As in, the stroke length that the scanned in image had, this has caused problems because the scanned in image is so large, when reduced to a more mangeable size, the stroke thickness is changed. Additionally, i believe that some of the capitals don't neccessarily conform with the lower-case and will require a re-design.

There are several alterations I will make for my 4th artefact. First one being making sure the stroke thickness is the same for all characters, as upper-case and lower-case appear to differ in this aspect. Second change I will make will be to reduce the angle of the curves I have used for some letters, as well as the overall width to gain a more consistent appearance. In my next artefact I should take all these aspects into consideration, as well as how the serifs will affect the spacing of the letters as I will widen them by one stroke.  

Despite these changes, I will not be making any changes to the way I create the font as a whole, the only change I shall make is the addition of the serifs, which I will do in Illustrator. This is because the additional measuring required is inefficent compared to the amount of time it takes using the software.

Client Project Update 2

As part of the design, I was going to allow the owners of the Stonebridge farm to post tweets as news updates that would feature on the homepage. So far it looks like this:

The way this tweet is made, is that the top section (anything above the text), is a static image placed on the page using css and html. The same applies for everything below the text, as that is another section of the speech bubble that has been split up. The section in the middle is a 1pixel wide slice of the PNG file I made in photoshop, that has been assigned as a background-image in css, and then repeated within a wrapper defined in the stylesheet to stop the repeating image over-flowing.

The image above is a direct screenshot from firefox. As you can see, I have a gap between the top section and the repeating middle section. Which i need to get fixed. I've also decided to change the overall layout of the chosen design, purely because I hadn't thought through what the website would look like to users with a resolution bigger than 1024x768, which is the optimal resolution to view the website with.

Instead of the dirt background stretching as far as the page is wide, everything will be set in a box and the dirt background will be cut off, a long with the previously extending navigation bar and footer. This means I will have to chose an appropriate colour for the background, as I would like it so that the contents background isn't the same as the site's background.

Currently downloading Adobe Flash, and will proceed with producing the imageviewers and map once it's installed. I also need to gather content, such as taking photo's and statements from people who work at the farm, this can be done when I am back in Nottingham.

Client Project Update

Just going to quickly document what I've done, or what I've attempted rather. Will update in more detail tomorrow.

Basically made the images for the navbar, both for when you hover over them and vice versa. Centred them. Also found a temporary image for the dirt background and a good flash tutorial for the image viewer.


It's been a while so this is a long process. I currently need to make the dirt background for the image viewer. I think instead of having the dirt stretching across the page indefinitely, I'm going to box it off and only make the navbar appear that way using background-repeat. I think it'll make it look more polished.

Will update with images tomorrow!

p.s. oh and I've also created each page file and found a good flash tutorial for an image viewer to go on the gallery page.

Everitt Regular V3 -

Below are the edited version of Pixel V2, the second of my artefacts. Specifically, this is the sans-serif version of the font. I believe that this counts as one of my my artefacts, however this isn't the finished version.

I have made a few changes from Pixel V2, which I'll address now.

The first change I made was to remove the serifs that I had used in the previous version. These can be found in my older blog posts on letters such as a, b, d, g, etc. I was told by shaun to remove these as they are not consistent enough with the rest of the font. This was evident as some letters did not feature these additional serifs. Because of this removal I had to make some changes to the characters themselves, and re-design some of them, these can be seen below. I have not included them all, as there are around 18 glyphs that differ from the original. However these are the most notable.

 

 

I would like to explain that the grid is a different size because some of the originals weren't re-sized when they were made. However the x-height has not been adjusted for any of the characters. 

The majority of changes that I made were removing the serifs off the edges of the characters, to give them a more rounded appearance that was consistent with the overall style of the font. Other changes I made included:

• Some characters width being reduced. I decided that while keeping the curves constant, it was completely neccessary to have the same 'run-up' to the curve. Addtionally, by making them more squashed it meant that taller characters weren't so out of place alongside the wider ones. 
• The angle of curvature reduced/increased. Examples of this can be seen on the u above, where the inital curve takes a much wider angle as opposed to its predeccesor. I did this so that the changes I made to the shape helped the overall aesthetic of character remain consistent with the rest of the font. Other examples can be seen on the m and n characters. 
• Made the Upper-case more consistent in terms of how they relate to the lower-case character's x-height. For example, any horizontal lines that are used in the upper-case now sit directly above the x-height for all characters.

These are the changes I have made to the majority of characters, however there are still changes that I need to make in relation to the upper-case, explained below.

There are a few problems that I have noted while testing this from my own computer, mainly with the Upper-case glyphs. I believe that for the most part, the upper-case is the right height, but maybe could benefit if some of the characters were a smaller width. Additionally, I believe some characters will need to be completely re-designed in order to fit with the rest of the font in terms of how they are styled. Characters such as the upper-case N and M, do not fit with the way the rest of the font looks. They are too jagged and harsh, they do not fit with the rounded style of the font.

As you can see, below I have screenshots of what the font looks like when in size 10 and size 20. Some characters are too wide or too squashed. This is mainly evident within the lower-case.

I believe that this version of the font is an improvement on the last version, at smaller sizes the font looks readable, despite the inconsistencies between the appearance of upper-case and lower-case characters. I will update once I have re-designed and implemented these changes.

Artefact 2 – Evaluation

I believe my second artefact was an improvement on the first. This was reflected in the feedback I gained from Shaun, who expressed the same sort of feelings towards the font that I had. That my second font was much more attractive/readable than the first.

I believe that my second font was an improvement as it was much more applicable to a wider range of uses. This was something Shaun also expressed, as the rounded nature meant that the font was more aesthetically viable for public use. There are improvements that I can make however. For example, learning how to properly kern my font as well as not mixing sans-serif with serif, which was also feedback given to me.

The process was effectively the same as my first font, however I was aware I didn't have to outline my final sketches in great detail, or outline them in black ink (as to stand out when scanned in).

It's not what I completely expected, although the general feel of what I was trying to achieve is there. A rounded and wide font. I will have to re-design some of the letters as at smaller sizes it appears as though some characters are a different height, when in reality they are exactly the same. The font works, although lacks some characters such as numerals and punctuation.

While the process was lengthy, it is the only process that is viable (as far as I'm aware). However, this isn't a significant problem as the majority of time spent on my first font was dramatically reduced for my second because I knew the process.

In conclusion, I think my font still needs work, but it is slowly taking shape through my own development.

 

Few changes from the first version, I've tried to keep the stroke thickness the same throughout the entire font. I've also included the punctuation glyphs. 

This time around, I've decided to try and imagine what this font would look like on a computer screen. I think some of the characters need some work, for example the w is probably too wide, most notably the capital W. 

I've also tried to keep things consistent, and some capital letters mimic the lower-case, rather than having a different style. Looking at my font as a whole, I think it would be better if I didn't include the little flicks (usually to the top left of the letter, see J, R, M, P and N). Mainly because a lot of the lowe-case letters have these flicks, yet their capital counter-parts do not. Therefore I think it would be more consistent if I removed the flicks from the capitals entirely, as it's only the minority that have them. I learnt my lesson this time and these only took collectively about 3 hours (I have to draw in pencil and then draw around the outline in pen so the lines are visible), leaving me more time to do the blown up versions. Which i think will be useful as my last font, I used those drawings as a reference point.

Everitt Pixel Regular is born - first font done

First aretfact is now done, before i do my evaluation, I should explain what happened between scanning the images in and being ready to import in to fontlab. 

As with all things when you start out with something new, you make time-consuming mistakes just down to inexperience. Such things have happened to me in the past 5 days. For example, it wasn't completely neccessary to draw each letter out by hand on a landscape piece of a4 beforehand. While they did act as a good reference point if I lost my way, the I could always look back and confirm anything i needed. 

As good as that is, I think next time I will spend less time on the drawings and depending on time, maybe not do them at all, as everything can be drawn in Illustrator and the path imported in to FontLab. Mainly because the a4 drawings are too large when they're scanned in to and subsequently take time to resize. I had to re-size every single character individually because of my error. They then need to be re-scaled with Fontlab in mind as some simple maths came in useful when calculating from points/millimeters to UPM (Unit Per Metre), which is the unit fontlab calculates size in. 

This required finding the em square of my font (ascender height + descender height). Initially I thought that the ascender is usually the same height or taller than the caps, but with my font the ascender was lower, which caused some confusion as I wasn't sure if I should use the caps height for em square as it is the tallest value. This is the maths that makes sure the font is the right size when it's finally generated. 

After resizing the characters so they are all in proportion, it's a case of copy and pasting the shapes from Illustrator to photoshop. No .eps file required, which I thought would be the case, but apparently not. 

Once the images are in Fontlab (and after altering the caps height, ascender height, x-height, and descender height in the options), all that has to be done is lining up the paths with the guides and setting the spacing bewteen each letter. However I was disapointed to find that I could only export in TrueType instead of my personal preference OpenType. 

Evaluation

Artefact 1 Evaluation – Daniel Everitt

Why did I chose the ideas that I did to make a font? They seemed like the easiest in terms of measuring things out, I didn't want to over-stretch myself with a font that was to difficult to produce.

One thing I believe would've enhanced my font, would be to make every stroke the same thickness. I used straight flat edges and differing measurements for stroke thickness. Different thickness’s could have been useful in a fluid font, but not for such a linear one. Because of this, you can pick out the varying strokes at small sizes, making my font clunky.

Another mistake I made, was neglecting using diagonal strokes, instead of purely horizontal and vertical strokes. You can see the difference between the capital V and the B. Next time I should try to visualize how the letter may look when they are decreased in size, and design accordingly.

I should have used more flexible letter widths. While I think this was partly a good decision for letters like m & w, it also meant that some characters are negatively effected by it like the c, a, y and z. Next time I should research in to character widths and find out if there are equations that would calculate the appropriate width. Failing that, do what looks good.

I also miscalculated the x-height of the i & j characters. The top of the stems should be level with each other. The descender looks squashed, which might indicate wrong measurements.

Next time, I will know that my measurements must be finer, and the decisions I make must consider the overall aesthetic of the font, I think that this time around I was focused on the wrong things, and therefore neglected the basic essentials.

Scanned in drafts + Illustrator + Changes

So I've scanned in the entirety of Pixel, a-z & A-Z, and also touched up the images so they're not as noisy. 

After scanning them in, I opened the jpeg files up in photoshop, as the scanner did not give me the option to scan in bitmap format (although it allowed me to scan it in purely black & white), and ironed out any rough edges, although I didn't spend too long doing this as each drawing is only being used as a guidline. 

Additionally, I did try drawing over the scanned in lines with the line tool, and while this worked really well, all in all it wasn't beneficial enough for the amount of time that was consumed doing it.  So instead I erased any over-lapping lines and rough edges.

After smoothing out the letterforms, I re-sized them to a width of 1500px. In hindsight, this probably wasn't the best idea. It doesn't save me any time, nor is it an accurate way of getting everything the same size,b in fact it's probably detrimental to the entire process as not only have I spent time re-sizing them and saving them, I also have to re-size the image in Illustrator so it is the same size as everything else.

I've started doing some work in Illustrator, I've had some problems with it. First of all, I can't find out how to cut a shape out of an existing shape. So for example letters like b, o, and a, this has been a problem. I've gotten around it, but I'm not sure if the method I've used will work. Currently I've drawn the initial shape and then drawn the shape that I want to cut out, on top of the initial shape. I predict that when I finally import the shae into fontlab, it's going to cause problems if I leave it the way it is. 

Additionally I've also made some changes to some of the letter. Specifically the i and the j. When zoomed out, these characters looked out of place, so I looked at the x-height and the ascender height and then top of the stem was a different height to the x-height and was way too close to the ascender height. Basically hanging around in no-mans land. So I lowered the stem, changed the k accordingly and also documented the new sizes so that i can make subsequent changes to all the other lower-case characters.

Finally I've also managed to install the full copy of fontlab and illustrator, I need to find out how to import the shapes I draw, into font lab. The thing that is taking up the majority of my time is learning new processes and figuring out solutions to any problems I can encounter. Currently trying to find out how to import correctly into fontlab using .eps files instead of simply copy and pasting from Illustrator.

Final Draft of Pixel

 I've drawn up the basic character set for Pixel. Upper-case and lower-case are both done.

Obviously this isn't all of it, here's some pictures of a few of the sheets, I just didn't want to upload about 20 images of basically the same thing. 

I have to now have to scan it into a computer in bitmap format, import through photoshop and iron out any rough edges. This includes removing the pencilled in guidline I drew for a more accurate representation of my draft copies. After that it's a case of importing it in to Illustrator a vectorizing it and then also importing it in to whatever fontsoftware I can find. Before I can conduct research in to how effective my font is, I first have to make it so It can be printed on paper, rather than the subjects evaluate the font in it's unfinished form. That to me would result in innaccurate results.

Hoping to get some results by monday at the earliest. Depending how difficult fontlab is to use, earliest time I can expect to have a font usable on a computer is by Monday.

Upper case drafts

Upper-case drafts for regular and pixel.

I've decided against doing an Upper-case for the 'gothic' version. My reasons being that drawing them out by hand simply takes up too much time, more so with the gothic version as it is less conventional, it therefore takes more time to make the letters look right, and make them appear as though they should be of the same font. If that makes any sense. As for numerics, I'll draw those up once I have the these three fonts done with the letters, as they are not an essential part of the font. Same applies for grammar.

I think both of these turned out well, especially the pixel upper-case. Although that is expected, as not much can go wrong with those straight edges. This is the only font that I wouldn't change anything from my initial ideas. I think they all fit well together and the spacing is just about right for the effect that I wanted to achieve. Which was a tall font that appeared as though it had been drawn out by hand, despite it's square appearance.

As for the regular upper-case, I may have to tweak some of the characters, for example the K is looking a little bit wonky and the Q looks slightly out of place. Other than that the only thing I am considering changing is the overal width of the characters as I am happy with the height and spacing.

Third Font Draft

These take longer than I initially anticipated. Uppercase coming soon. 


This was a more difficult font to fully realize, which I still don't think I've accomplished. Definitely needs development particularly on the following characters, which I think are a bit sketchy. No pun intended. 

• c, e, g, o, x, y, w

These were the characters that I had the most trouble with, especially the c, since a and b have straight edges, I tried to incorporate that in to the c glyph, with little success. (See Below)

Above: Trying to draw the letter c in keeping with the rest of the font

I do like this font, and I think that it is readable, although that being said I have no idea what it looks like when at a smaller size. But currently I think it could at least be used, possibly, for larger scale work. I've tried to create my own version of a modern day Gothic font. While not being too old-fashioned and making some letters look almost completely different to their Roman counter-parts, I've tried to keep some resemblance. 

Another thing that may need change is the descender height. Mainly to contrast with the high ascender's but also because the elongated letters look not out of place, but just wrong. The J for example is far too elongated than is necessary and would look a lot better if it was shorter. I want to emphasize height with this font as I think that attribute lends itself to achieving an elegant font.

Finally, I would too add that I think it's important to keep an element of hidden consistency when designing a font such as this, while each character may be vastly different, there are key give-aways that link the characters together and make them look as though they belong in a set. This idea needs tweaking and development before that happens in my opinion, although we'll see what sort of feedback is given. 

Second Font Draft

Don't know why, but I like this one. 


Unlike a lot of pixel fonts, I aim to keep this at a relatively large size, as opposed to shrinking it down so it's similar to the fonts here: http://www.dafont.com/bitmap.php


Those fonts have been designed using individual pixels, I would like to make it appear as though this font has been done as well, while still retaining indication of it being drawn by hand. For example the diagonal lines on the v, j, and l characters. I will be getting feedback on these fonts all at once to save time, also it prevents me from repeatedly asking people to look at my fonts, when I could just show them all at once. 


Again, these are just rough drafts, the lines are meant to be perfectly in line with eachother, however sometimes that isn't possible when drawing freehand. These design serve their purpose, and that was to see how each character could look when it's finished. I will do the uppercase when I've completed the next draft.  


Peace.

First Font Draft + Update

This is the first draft of all the lower-case letters for one of my proposed fonts. I'm aware that I'm very behind at this stage, and so I'll be working on this for the next week while I can leave my client project sidelined for a while.  I aim to produce at least drafts of each character, upper and lower-case (including numbers and punctuation) by the end of the week, which will correspond with a gantt chart that I'm creating. It's helped me stay on top of my client project, so I figured I'd make one for my prp as well to help me keep track of what I'm doing and how long I have left.

In case you're wondering why i'm not producing the font entirely on computer, I discovered that I actually need to buy the software in order to export font files. Additionally, I believe this may get me more marks. I do still need appropriate software to convert my bitmap images in to font files, and to smooth out any rough edges, but overall despite being more time consuming, I prefer the method of producing fonts. Mainly because I can focus on drawing a lot longer than I can focus on pixels.


Additionally you may also notice that the image is a little bit chopped up. This is because for some characters, I couldn't produce the glyph first time and had to scrap it and start again. Chopping it up and removing the duds just gives me a better overall picture of what the font looks like as a whole.


Finally, this isn't all I'll be doing before producing the font, I aim to get feedback from a diverse group of subjects and then take their feedback into account and produce larger versions of each character so that when it is finally scanned in, the resolution will be higher and therefore it will be easier to manipulate in illustrator.