During beta testing and evaluation, many users have complained to me that they cannot get user or web preferences working. This invariably turns out to be a problem with the formatting of a preference as 6 spaces, *, another space, and the Set = syntax.
Most are trying to copy what they see in the rest of the file, which is 3 spaces = 1 tab.
Other than this being confusing to users, I'm not sure it's a real "bug," but I'd like to vote for all .txt file tabs to be converted to 3-spaces.
I agree, but Will suggests that there might be othter issues (given direction i'm willing to write the 10sec script) -- SD
There should be no other issues; 3 spaces and one tab are synonymous. Good idea to tidy it up, tho. SVN 6905 CC
Sorry, but this was no good idea at all for plugins that are backwards compatible and got broken content now at least if not broken as their
settings are not readable any more by a beijing or cairo engine.
So there's no way to resolve this going forward for Dakar? It looks to me like you fixed, then backed this out. As a user I must reject this solution...can there be translation done in the presentation layer, perhaps?
I backed out the changes to the plugins topics; but the rest of the docs now use spaces exclusively.