Have you looked at what happens to the files whenyou remove the portal.css and default.css files..
I believe the skins don't work - I could be wrong, I haven't tested lately but I remember having problems with css and how it's read and you need to have the portal.css file and the default.css file in the correct locations.
You see, in the Admin/settings page - if you want to edit the css editor on the fly - it's reading the css file sitting in the portal alias... and it throws hissyfits if it can't find that css file.
You can leave them empty, which would have the same effect as merging, but make sure you put ALL the classes into the skin.css file.
That's my two cents worth ... i've done plenty of style sheet crying over having duplicate entries in different files.. *sigh*.. yep... makes me cringe thinking of the mistakes I made!!!
So in summarising... sure merge the content, but leave the files in tact.
Nina Meiers
Nina Meiers