Skip to Content.
Sympa Menu

cc-devel - [cc-devel] [ cctools-Feature Requests-2276001 ] Skin string replacement happens in 2 places, not 1

cc-devel AT lists.ibiblio.org

Subject: Developer discussion for Creative Commons technology and tools

List archive

Chronological Thread  
  • From: "SourceForge.net" <noreply AT sourceforge.net>
  • To: noreply AT sourceforge.net
  • Subject: [cc-devel] [ cctools-Feature Requests-2276001 ] Skin string replacement happens in 2 places, not 1
  • Date: Fri, 14 Nov 2008 12:29:00 +0000

Feature Requests item #2276001, was opened at 2008-11-13 03:37
Message generated for change (Comment added) made by fourstones
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=559969&aid=2276001&group_id=80503

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: ccHost
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Dave Crossland (crossland)
Assigned to: Victor Stone (fourstones)
Summary: Skin string replacement happens in 2 places, not 1

Initial Comment:
Skin string replacement happens in 2 places, not 1, and having just 1 place
would be easier to manage.

/public_html/ccskins/shared/strings/*.php are the default strings.

/public_html/customsitename_files/skins/customsitename-skin/strings/customsitename.php
and
/public_html/customsitename_files/skins/customsitename-skin/strings.php

are where to declare replacements.

Some of ccHost respects one and some respects the other, so OFLB has
duplicated the contents to be sure. Ideally there would only be one.

----------------------------------------------------------------------

Comment By: Victor Stone (fourstones)
Date: 2008-11-14 04:29

Message:
I'm moving this 'feature request' because this was done, in fact, "by
design" - there are some strings (like "Skip to content") that are strictly
for a specific skin and have no business in the globally shared 'string
profile' - it's possible the better way to handle this would be to create
template-tags (like those in 'admin/templatetags') which only the skin
would understand.

Either way, we need a way for a skin to introduce it's own strings,
particular to the way it presents things and not force every skin maker to
put strings into the whatever the currently selected global string profile
is.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=559969&aid=2276001&group_id=80503




Archive powered by MHonArc 2.6.24.

Top of Page