Changing font for the whole .pdf document generated by LaTeX

The font changing for the whole document generated by LaTeX could be done by specifying the following line in the LaTeX preamble:

\renewcommand{\rmdefault}{cmss}

from here

If you want to use non-default font, you should to install the corresponding package first. The "winfonts" package contains the following fonts:

Arial           Franklin Gothic     Tahoma           Comic Sans

Georgia             TimesCourier New     Palatino Linotype   Verdana

You can download it from here:

http://www.ctan.org/tex-archive/fonts/winfonts/

The readme file on how to install the package is also included.

Now you can use a non-default font for the pdf:

\renewcommand{\rmdefault}{verdana}

If the source LaTeX document is genereted by Sphinx you should add the line in the end of the "latex_preamble" in the config.py.

License is not displayed error in WIXUI_Minimal.

From here

There is a known issue with the rich text control used to display the text of the license file that can cause the text to appear blank until the user scrolls down in the control. This is typically caused by complex RTF content (such as the RTF generated when saving an RTF file in Microsoft Word). If you run into this behavior in your setup UI, one of the following workarounds will fix it in most cases:

• Open your RTF file in WordPad and save it from there in order to remove the complex RTF content from the file. After saving it, rebuild your MSI.
• Use a dialog set other than the WixUI_Minimal set. This problem typically only occurs when the license agreement screen is the first one displayed during setup, which only happens with the WixUI_Minimal dialog set.

About SharePoint List view customization

Customizing the user experience of SharePoint: Lists, Custom list forms and CAML views:
http://sharepointmagazine.net/technical/development/customizing-the-user-experience-of-sharepoint-lists-custom-list-forms-and-caml-views-part-3-of-6

Limitations of STSADM -o export/import related to publishing sites

The original article is here

STSADM -o export/import is often used to split site collections into multiple pieces when they reached a certain limit. Or to do the vice versa and consolidate multiple site collections into one larger one. Both of these actions work fine as long as the migrated content does not use the publishing feature.
For site collections that make use of the publishing feature it is not supported to migrate root sites into sub sites or sub sites into root sites.
The reason for this limitation is that the publishing feature stores vital information like page layouts but also various properties like information about variation, reusable content and so on in the root site of a site collection.
When migrating a root site into a subsite the imported content will link to the new location of the previous root site. E.g. the page layout URLs will afterwards point to the page layouts library in the sub site and not of the root site which does not work as the publishing feature requires these items to be in the root site. So additional actions like moving the page layouts to the root site and adjusting all page layout urls would be required. Similar things would be required for variations and reusable content.
On the other hand when migrating a sub site to a root site it gets even worse: in this situation important content which was stored in the root site of the site collection is no longer available as the sub site does not contain the necessary information as they haven't been exported in the first place. So after importing the subsite as new root site items based on the publishing feature will be non functional.
Be aware that this limitation will also affect sites with custom features which store information outside the current site.
Valid migration scenarios when using the publishing feature are the following:

• export the site collection starting at the root site and import as root site into a new site collection
  (using a custom application you can specify which sub sites to export if you would like to avoid to export all of them)
• export sub sites of the site collection and import them as sub sites into an existing site collection that has the publishing feature enabled