I've only met 2 people in my life who are as fussy as me about food. Thought I would share some details. I've narrowed it down not to issues with taste, but usually texture. The black bullet points identify things I am not very fond of at all.
Potatoes - mushiness
Roast potato - hot and/or crunchy is OK
Chips - salty and/or crunchy and/or hot is OK
Peas - mushy
In burgers/tuna melt - OK - because they baguette is also crunchy
In tuna mayo sandwich - not OK - because they are crunchy, when sandwiches aren't crunchy
In lasagne/bolognese - not OK - because it is meant to be smooth
Sweetcorn - only on its own, not in/with anything - because it is both crunchy and smooth
Peppers, chillis, cherries - texture of the skin
Cherry flavour is OK
Anything moderately spicy is not OK
Egg mayo - texture of egg pieces
Banana - mushiness
Banana-flavoured foam sweets are OK
Not a fan of banana milkshake or ice cream
Chocolate ice cream (e.g. Ben & Jerry's)
Normal chocolate is OK
Melted chocolate is OK
Chocolate anything else is OK
Coffee, tea and any other hot drinks - can't handle hotness
Hot chocolate is okay when mild
Coffee flavour is not OK
Breakfast cereal with milk - soggyness
Separate milk in a glass, sipped with a spoon of cereal is OK
PC: Dell, Alienware, HP, etc.
Mac: Air, MacBook, iMac
Protection & Backup
Ease of use
Third party support for applications/compatibility e.g. gaming, apps
Technical Support (availability/quality)
Had a very bad cold yesterday but wasn't troubled by my runny nose today hardly at all (very minor sniffles and slight sore throat at times and tiny bit of a headache but nothing that interfered).
Here's a list of what I did yesterday to combat it:
Here are some results of the 'best' antimalware solutions based on their ability to detect a new virus that entered the world wide web on 1st June 2012. So yes, this isn't an accurate method, but from the results you can clearly tell which companies may be faster at getting out definitions.
F-Prot - W32/FakeAlert.MC2.gen!Eldorado
NOD32 - a variant of Win32/Adware.WintionalityChecker.AF
Update 1: There is a solution that may work for some people from Microsoft (released 18/02/2013, nearly a year after this post). Download the Fix-it from this page and see if it repairs the file for you. Update 2: Also there is a similar blog here which explains the same as I've done (also dated later but describes in a different way)
There is a bug in Word 2010 I've come across for the third time now to do with XML validation on documents when they are saved over a network.
You may have seen this before:
The file 113 Honey Lane brochure.docx cannot be opened because there are problems with the contents.
Some online articles report this as a problem with the table of contents, however I've worked with documents that don't have a table of contents. Also I cannot see any Microsoft response to this issue and I hope to get their attention to get this fixed.
Word does have an 'Open & Repair' option, however this only tries to read text from the document, so this doesn't help us at all and leaves us stranded with a 99.99% valid XML document but unable to use it - that is one of the pitfalls of XML I guess. But really this is a bug that Microsoft needs to correct.
How to fix
1. Extract the DOCX file using an compression program (i.e. 7-zip) to a new folder.
2. The 'Location' on the error dialog is where the problem is. However as it says Line 2 Column 0, well, Column 0 is right when the main body opens - which means the actual XML problem could be anywhere. If we knew where it was, we would just need to go to Line 2, Column 286 or whatever, and correct the XML. However when it is like this, we need to validate the XML instead. I recommend Oxygen XML Editor:
3. Open up Oxygen and open the word/document.xml file from the extracted folder.
4. Validate the XML.
5. Right at the bottom of the validation report are the important errors. Some errors are permittable.
The ones in red are the ones we need to fix. The ones in green are fine.
6. Fix the XML. CTRL+L can take you to the location in blue (Line 2, Column 365...) Here is one example of XML that needs to be fixed but in general the problems I've seen have involved incomplete tags and missing closing tags.
Here, the < mc:Fallback > tag doesn't have a closing tag. Also, there is no closing < /mc:AlternateContent > tag before the new < w:p >. Here is the corrected version. The first 4 validation errors from above, I actually couldn't fix, so I just removed the < mc:Fallback > block altogether (it is a fallback so it is not important anyway).
We can see that the same block is now validated to be OK (there is no longer a red dotted line under the tree leaf on the left). I had to add 2 closing elements and Oxygen actually autocompleted them as soon as I typed < / so I didn't need to type out the whole thing ;)
After saving and validating again we can see there are 2 more errors somewhere else in the document, again these just need some more closing tags.
7. When it validates so there are no more major errors (not to do with namespaces/context), just zip up all the files again in the extracted folder (must be using the ZIP format, other parameters don't matter) and rename to docx. Now open it in Word and the error is gone.