ENSURING THAT VirtualFont CAN BE CREATED ONLY VIA FontManager
Revert "ENSURING THAT VirtualFont CAN BE CREATED ONLY VIA FontManager"

This reverts commit c1de9cbb66f5c59db121310cfc9dc790b87e06b4.
Rendering PROJECT: FontManager::getFont() IS NOW RETURNING A shared_ptr
Rendering PROJECT: FontManager::getCachedLineLayout() AND LayoutCache::getLineLayout() ARE NOW RETURNING A shared_ptr<LineLayout>
Rendering PROJECT: REFACTORING: getFont() -> getCachedFont()
Rendering Project: OPTIMIZATION: USING auto& INSTEAD OF auto IN ORDER TO AVOID UN-NECESSARY COPIES
Rendering PROJECT: USING shared_ptr<ActualFont> In FontSet — PREPARING THE TERRAIN FOR FontManager::removeFont()
Rendering PROJECT: FINALLY FOUND A WAY TO USE PROTECTED CONSTRUCTORS FOR VirtualFont AND ActualFont
Rendering PROJECT: FontManager::loadGlobalMap() CAN ONLY BE CALLED ONCE (FURTHER ATTEMPTS WILL THROW...)
Rendering PROJECT: REDESIGN OF THE ActualFont LIFE-CYCLE
ROLLING-BACK USAGE OF shared_ptr FOR STORING ActualFont IN FontSet, AS IT PROBABLY WON’T BE USED BY FontManager::removeFont()
Rendering PROJECT: POSSIBILITY TO CALL FontManager::unload(...) PER VirtualFont
FIXING REGRESSION WHEN USING new-chronotext-toolkit ON iOS (INITIAL SCREEN ORIENTATION…)
Rendering PROJECT: XML FORMAT REDESIGN - PART 1
Rendering PROJECT: XML FORMAT REDESIGN - PART 2
Rendering PROJECT: MORE ROBUST XML PARSING IN FontManager
Merge pull request #2 from arielm/develop

Develop