SharePoint content deployment issues

One of my customers recently faced 2 issues with content deployment. We were both unaware of the hotfixes that were posted to resolve them. Here's a quick summary of the issues.

Issue #1: Some special characters show up in the Published site:  and ’. Here's the MSDN article for the hotfix:
https://support.microsoft.com/kb/938536

The jargon in the article is somewhat confusing, but the relevant portion covering the above issue states:

Language-specific special characters are displayed incorrectly on Web pages of the destination site collection after you run a content deployment jobYou run a content deployment job to copy content from a source site collection to a destination site collection. Web pages in the source site collection have one or more columns that contain certain language-specific special characters such as ó or ê. After you run the content deployment job, you notice that the special characters are displayed incorrectly in Web pages of the destination site collection. You also experience this issue if you use the Stsadm.exe command-line tool to export content or to import content. This problem occurs if the special characters are encoded incorrectly.

 

Issue #2:

Violation of PRIMARY KEY constraint 'PK__#ExportObjects____22355A14'. Cannot insert duplicate key in object 'dbo.#ExportObjects'. The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery(SqlCommand command)
at Microsoft.SharePoint.Deployment.SPExport.CalculateObjectDependencies(Boolean linksOnly)
at Microsoft.SharePoint.Deployment.SPExport.FollowLinks()
at Microsoft.SharePoint.Deployment.SPExport.CalculateObjectsToExport()
at Microsoft.SharePoint.Deployment.SPExport.Run()

Here's the hotfix that fixes the issue:
https://support.microsoft.com/kb/936867

Generally the issue with searching for issues like these is to remove the specific info from your case. This is what bogged down my customer. To search for this one, I just queried on the portion here: "Cannot insert duplicate key in object 'dbo.#ExportObjects'. The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)"