--- a/Symbian3/PDK/Source/GUID-AFB1F350-C5D3-5495-AE20-1AA6888B6FB1.dita	Fri Jul 02 12:51:36 2010 +0100
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,26 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
-<!-- This component and the accompanying materials are made available under the terms of the License 
-"Eclipse Public License v1.0" which accompanies this distribution, 
-and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
-<!-- Initial Contributors:
-    Nokia Corporation - initial contribution.
-Contributors: 
--->
-<!DOCTYPE concept
-  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-AFB1F350-C5D3-5495-AE20-1AA6888B6FB1" xml:lang="en"><title>How
-to Insert Trace Points in a Component </title><prolog><metadata><keywords/></metadata></prolog><conbody>
-<p>Trace points can be added manually to trace specific-required events in
-the source code or component at build time. </p>
-<p>To instrument a component, the Instrumentor can use the methods given in
-the <filepath>epoc32/include/e32utrace.h</filepath> file. The UTrace API provides
-some basic information for each trace, but the Symbian developer has to define
-the payload of the trace. It is recommended the Instrumentor is consistent
-whilst adding traces in order to help the Trace Collector parse the trace
-output once it is on the host. For example, being consistent while formatting
-an Object ID or Object Name. </p>
-</conbody><related-links>
-<link href="GUID-D5984540-A411-52ED-B435-94C67F34ADD5.dita"><linktext>How to enable
-tracing</linktext></link>
-</related-links></concept>
\ No newline at end of file