two-column for bilingual pages

minusf · 2006-04-20 20:44:25

hi there,

i am trying to move this site to txp.
to signify that both languages are equally important the original design
was to put the identical texts side by side using good ol’ tables, like here .

i am quite at a loss how to do the same using css/textile.
i could make two 50% wide div’s in the presentation part,
but how do i get the texts to appear in those particular divs
from content/article side?

colak · 2006-04-21 05:54:51

minusf wrote:

i am quite at a loss how to do the same using css/textile.
i could make two 50% wide div’s in the presentation part,
but how do i get the texts to appear in those particular divs
from content/article side?

I would think that you can achieve that in 2 ways.
a. One div reads the <code><txp: article /></code> and the other reads <code><txp: excerpt /></code>.
b You have the columns divs in your “write” tab.

I guess it depends who’s going to be updating the site and their level of xhtml

minusf · 2006-04-24 09:12:20

thanks for the ideas…

a. is interesting :) but i think would be most confusing for my lady editor.
b. seems ok, but txp does not really “encourage” putting div’s into the article, does it? as far as i know, textile doesn’t even have a div “command”.

i’ll try to go with b. what a challenge! :)

jm · 2006-04-24 09:34:55

Going out on a limb here, but here’s a thought. This probably won’t work, but…

1) post the first language to it’s own category (language1)
2) immediately after, post the other language version to its own category (language2)
Just make sure the time stamps are similar…I think.

The page template might look like this:

</div>
</code>

CSS:
<code>
#container {
width: 80%; /*or something*/
margin: 1em auto;
}
#language1 {
width: 49%;
float: left;
}
#language2 {
width: 50%;
float: right;
}
</code>

——

Here’s a really ugly solution, just for kicks. Place a frame on the right for the translated article. Have the frame source as http://translate.google.com/language/<txp:article_url /> (a made up tag). That’s what I call innovative :P.

colak · 2006-04-24 13:56:08

b. seems ok, but txp does not really “encourage” putting div’s into the article, does it? as far as i know, textile doesn’t even have a div “command”.

Hi minusf
It might not have it but it allows you to manually insert it. It depends how comfortable your client is with some simple xhtml

ie
<code><div class=“lang1”>content…</div>
<code><div class=“lang2”>content2…</div></code>

mrdale · 2006-04-24 14:41:30

Seems like option A would be ideal, as it keeps the article grouped as one item, rather than having to deal with duplicate IDs, text-only URLs and editing areas.

it would also allow for you to create the division between the articles in the Article form.

If you can get your editor used to the idea, I think it would be functionally and administratively superior.

minusf · 2006-04-25 21:29:16

It might not have it but it allows you to manually insert it. It depends how comfortable your client is with some simple xhtml
ie
<code><div class=“lang1”>content…</div>
<code><div class=“lang2”>content2…</div></code>

the problem is, that this works fine as long as there are no paragraphs
or some other more complicated constructs inside the div. as soon
as i put something more in, txp fills in p’s everywhere, even surrounds
the div’s with it.

it seems that the exceprt/article approach is better, but i’ll keep playing with it.

minusf · 2006-04-25 21:53:48

call me a html/css traitor, but the table approach is not bad either :)
i guess it’s just one of those cases when the table layout is simply
easier and better. i might be wrong of course…

colak · 2006-04-26 05:41:24

Hi minusf

the problem is, that this works fine as long as there are no paragraphs
or some other more complicated constructs inside the div. as soon
as i put something more in, txp fills in p’s everywhere, even surrounds
the div’s with it.

textile does not wrap with a p if you leave a space in front of the first word.

it seems that the exceprt/article approach is better, but i’ll keep playing with it.

I would tend to agree with you as it will be easier to maintain. As excerpts are included in the feeds it would be a choice for you about which language you wish to syndicate your site with

colak · 2006-04-26 05:47:21

minusf wrote:

call me a html/css traitor, but the table approach is not bad either :)
i guess it’s just one of those cases when the table layout is simply
easier and better. i might be wrong of course…

You could emulate divs to present like a table. in its bare bones what I would I understand you need is 2 floating divs 48% width each. As simple as a table. For titles of articles (not mentioned in your queries) you could use custom fields (having in mind that they are not included in the search).

Textpattern CMS

Textpattern CMS support forum

#1 2006-04-20 20:44:25

two-column for bilingual pages

#2 2006-04-21 05:54:51

Re: two-column for bilingual pages

#3 2006-04-24 09:12:20

Re: two-column for bilingual pages

#4 2006-04-24 09:34:55

Re: two-column for bilingual pages

#5 2006-04-24 13:56:08

Re: two-column for bilingual pages

#6 2006-04-24 14:41:30

Re: two-column for bilingual pages

#7 2006-04-25 21:29:16

Re: two-column for bilingual pages

#8 2006-04-25 21:53:48

Re: two-column for bilingual pages

#9 2006-04-26 05:41:24

Re: two-column for bilingual pages

#10 2006-04-26 05:47:21

Re: two-column for bilingual pages

Board footer