Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#13 2011-12-17 02:35:53

phiw13
Plugin Author
From: Japan
Registered: 2004-02-27
Posts: 2,360
Website

Re: 2012 Textpattern Default Theme

Question: would it really kill you to add some additional support for Gecko 1.9.2 based browsers (Camino 2.1, Firefox 3.6 [*]) in your stylesheet ?

(it boils down to adding -moz-border-radius and -moz-box-shadow)

[*] I still see a fairly high number of Fx 3.6 in stats across various sites…

Last edited by phiw13 (2011-12-17 02:37:40)


Where is that emoji for a solar powered submarine when you need it ?

Offline

#14 2011-12-17 09:34:42

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,517
Website GitHub Twitter

Re: 2012 Textpattern Default Theme

Hi Philippe, I could do but since those are only aesthetic I’m not sure I should. If there are any structural errors I’ll certainly investigate those.

FWIW I really like camino and used it a lot back when it was still called chimera so I’ve nothing against it.

Offline

#15 2011-12-17 09:41:36

phiw13
Plugin Author
From: Japan
Registered: 2004-02-27
Posts: 2,360
Website

Re: 2012 Textpattern Default Theme

philwareham wrote:

I could do but since those are only aesthetic I’m not sure I should.

given that you already have a buch of -webkit-box-shadow, why not do it ?

If there are any structural errors I’ll certainly investigate those.

None that I’m aware off atm.


Where is that emoji for a solar powered submarine when you need it ?

Offline

#16 2011-12-17 10:15:13

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,517
Website GitHub Twitter

Re: 2012 Textpattern Default Theme

phiw13 wrote:

given that you already have a buch of -webkit-box-shadow, why not do it ?

I’d quite liked to have dropped -webkit-box-shadow too.

OK, I’m persuaded (it’s hardly any more code) – gecko 1.9.2 support from this commit. We can always remove that rule in a later release when Camino moves to a newer gecko.

Offline

#17 2011-12-17 11:54:13

phiw13
Plugin Author
From: Japan
Registered: 2004-02-27
Posts: 2,360
Website

Re: 2012 Textpattern Default Theme

philwareham wrote:

gecko 1.9.2 support from this commit.

Thank you. :-).

[off-topic]

… Camino moves to a newer gecko.

which is something that will never happen, given that Mozilla Corporation killed embedding and did a few more stupid things, making it impossible to build Camino on more recent version of Gecko. An eventual Camino 3 will be WebKit based. Long story, not the place to discuss.


Where is that emoji for a solar powered submarine when you need it ?

Offline

#18 2011-12-17 12:05:32

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,517
Website GitHub Twitter

Re: 2012 Textpattern Default Theme

Oh ok.

Offline

#19 2011-12-18 09:30:17

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,517
Website GitHub Twitter

Re: 2012 Textpattern Default Theme

The theme has been updated to beta2, you can download it from GitHub as usual.

I worked through some improvements with Gocom, changelog since beta1…

  1. Removed favicon and touch icon meta links
  2. Single quotes on variable value attribute
  3. Removed format attributes from various date tags (improves localisation)
  4. Removed display of unneeded extra comma when category2 is set, but category1 isn’t
  5. Removed PHP-reliant copyright from footer as some installs might have PHP in page disabled (it’s now in the extras folder if needed)
  6. Prevent potential blacklist search term exploit
  7. Added search term to input value on search results page
  8. Added support for Gecko 1.9.2 browsers (Firefox 3.6, Camono 2.1)

I’m going away on vacation now without internet access until early January, but keep filing any issues you discover and I’ll work through them on my return.

Cheers, Phil

Last edited by philwareham (2011-12-18 09:30:36)

Offline

#20 2012-01-08 09:42:27

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,517
Website GitHub Twitter

Re: 2012 Textpattern Default Theme

Question for non-English speakers, is this going to work OK…

<strong><txp:text item="author" />:</strong> <span class="fn"><txp:author /></span>

Note the : in there, is this wrong to use for other languages?

Offline

#21 2012-01-08 15:29:11

RedFox
Member
From: Netherlands
Registered: 2005-03-25
Posts: 782
Website

Re: 2012 Textpattern Default Theme

Phil, maybe you’ll already know these sites (and methods) but I think they are a fine read:

Adaptive Images
The Goldilocks Approach

Offline

#22 2012-01-08 15:31:54

Pat64
Plugin Author
From: France
Registered: 2005-12-12
Posts: 1,471
Website GitHub Twitter

Re: 2012 Textpattern Default Theme

Hi Phil.

In french, : need a space before and after but I know it’s very specific and difficult for you with international support in mind ;)

Cheers,
Patrick


Patrick.

Github | CodePen | Codier | Simplr theme | Wait Me: a maintenance theme | [\a mi.ni.ma]: a “Low Tech” simple Blog theme.

Offline

#23 2012-01-08 16:44:39

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,517
Website GitHub Twitter

Re: 2012 Textpattern Default Theme

Pat64 wrote:

In french, : need a space before and after but I know it’s very specific and difficult for you with international support in mind ;)

Thanks Patrick, I think I may be removing the : altogether anyway because I get the feeling it is not used at all in certain languages (especially those with non-latin alphabets). Just need some further clarification from people more knowledgeable in these matters than I.

Offline

#24 2012-01-08 17:52:15

jakob
Admin
From: Germany
Registered: 2005-01-20
Posts: 4,140
Website

Re: 2012 Textpattern Default Theme

Might something like this work with css:

.container-class strong:after { 
   content: ": ";
   padding-right: .5em;
   }
html:lang(fr) .container-class strong:after {
   content: "\a0 : "; /* with nbsp added in front */
   padding-right: .5em;
  }

(using your respective container class name). That would be similar to another css-based approach for dealing with French guillemot quote marks.

For moodle, they suggested moving the colon to part of the translation. this would be like a gTxt entry for author_separator or something.

Last edited by jakob (2012-01-08 17:55:48)


TXP Builders – finely-crafted code, design and txp

Offline

Board footer

Powered by FluxBB