Not sure if this is the right place to ask this one...
I've just installed FlaggedRevs in the OOoWiki. It's working OK so
far... but one little thing has come up and I'd like to fix it.
Take a look at a random page like this one:
http://wiki.services.openoffice.org/wiki/Documentation/Administration_Guide
The "Current revision" div from the FlaggedRevs extension is floated to
the right. The OOoWiki also used floated divs for table of contents...
on the right. The result is that they stack up against one another.
Does anyone know how I can get them to stack on top of one another
instead of side by side as they are now? I've tried adding clear:both;
to the div for the table of contents box (the one that's floated right)
but that seems to have no effect.
C.
--
Clayton Cornell ccornell(a)openoffice.org
OpenOffice.org Documentation Project co-lead
StarOffice - Sun Microsystems, Inc. - Hamburg, Germany
>
> A large part of the problem here is that the translation needs of someone
> like me are quite different from the translation needs of someone who is
> translating an interface.
>
As I said my friend, it is more a matter of involving people than finding
technical ways.
Att, Nevio
2009/11/21 Kent S. Larsen II <kent(a)lusobraz.com>
>
> Hmmm.
>
> I think you are taking this quite defensively.
>
> My principle observation is simply that currently this extension is NOT set
> up to make it easy for translating anything but interfaces. It doesn't seem
> to have anything that helps explain how it would work otherwise, and there
> are NO examples of translating anything that isn't an interface.
>
> A large part of the problem here is that the translation needs of someone
> like me are quite different from the translation needs of someone who is
> translating an interface.
>
> My only reason for commenting is that you seem to be pushing a solution
> that isn't adequate to the job described -- you seem to believe that a
> system set up for translating interfaces should be adequate for translating
> documents -- and you haven't explained how it IS adequate. Come back to me
> when you have the explanation on the web somewhere and have an example so
> that I can see how it works.
>
> I'm not really looking for a solution at this point, so yes, I only see
> problems. What I do use on my wiki (combination of proofread page and
> doublewiki extensions) and elsewhere (Google translation toolbox) is
> adequate, but not ideal. Until I see something that is better, and,
> ideally, involves the input from someone who actually does the translation
> of documents (or better for me, whole books), I can't see a reason to waste
> much time looking through something that is only presented as a solution or
> "opportunity" for those who have completely different needs than I have.
>
> Kent
>
> At 8:12 AM +0100 11/20/09, you wrote:
> >Right. So I'll give it one last shot before you go try and create your own
> >extension in the next two years. It appears to me like you are thinking in
> >problems instead of opportunities.
> >
> >Let me translate some of the remarks you made, and provide some more
> >information:
> >
> >(1) 'to set up a page to be translated, you have to not only set it up as
> a
> >project, but break the parts of the page into individual translateable
> >chunks': Opportunity speak: Wow. This is flexible. You can choose to put
> >translate tags around the whole page content, where a parser will break it
> up
> >for you, but it is also possible to keep the awkward formatting away from
> >translators, and selectively keep out that formatting from the
> translatable
> >content. Would there be any chance that this can be done automatically? My
> >reply: sure. We are a little short on developers, but we are certainly
> >prepared to help you further develop on the Translate extension if you are
> >interested and able to.
> >
> >(2) 'whole thing seems extremely cumbersome and inconvenient': Opportunity
> >speak: I don't understand fully how to do this. At first glance it looks
> hard.
> >Can you provide some additional information? My reply: sure. We'd be glad
> to
> >help you. Please join us on Freenode's #mediawiki-i18n and we will see if
> we
> >can get any misunderstandings out of the way.
> >
> >(3) 'translatewiki.net currently doesn't have ANY documents or webpage
> >projects, only software interfaces': Opportunity speak: I cannot find
> which
> >content pages are available for translation at the moment. Do you have
> some
> >links? My reply: sure. See
> >http://translatewiki.net/wiki/Special:PageTranslation
> >
> >(4) 'the documentation needs to be re-written to make it clear how to use
> it'.
> >Opportunity speak: I cannot find the documentation. Where can I find it?
> My
> >reply: Ouch. You got us there. Having the little development resources
> that we
> >have, we have always invested in adding and improving functionality, and
> >documentation is outdated at best. On mediawiki.org it is not present. We
> >would appeaciate help in that area. Also see (2).
> >
> >Cheers!
> >
> >Siebrand Mazeland
> >
> >
> >
> >-----Original Message-----
> >From: mediawiki-l-bounces(a)lists.wikimedia.org
> >[mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Kent S.
> Larsen
> >II
> >Sent: Friday, November 20, 2009 4:22 AM
> >To: MediaWiki announcements and site admin list
> >Subject: Re: [Mediawiki-l] Translating wiki articles
> >
> >
> >Yes, I checked out the link.
> >
> >As far as I can tell, in order to set up a page to be translated, you have
> >to not only set it up as a project, but break the parts of the page into
> >individual translateable chunks.
> >
> >The whole thing seems extremely cumbersome and inconvenient -- it really
> is
> >set up to be used for translating a software interface and not actual
> >documents.
> >
> >As far as I can tell, translatewiki.net currently doesn't have ANY
> >documents or webpage projects, only software interfaces.
> >
> >If I'm wrong about this, then the documentation needs to be re-written to
> >make it clear how to use it.
> >
> >Kent
> >
> >
> >
> >
> >_______________________________________________
> >MediaWiki-l mailing list
> >MediaWiki-l(a)lists.wikimedia.org
> >https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
--
{+}Nevinho
Venha para o Movimento Colaborativo http://sextapoetica.com.br !!
I've enabled external images with the above statement in my
LocalSettings.php, and try many syntax (from help text googled from web and
mediawiki documentation). It appears nothing I've done has enabled external
images or link to them. Only the working link to an image is displayed on my
wiki page. I'm aware of notes that image links which do not explicitly look
(to mediawiki's parser) like an image will be treated as a link.
Is there any step missing from the magic incantations needed to get external
images? Thanks for any help.
--
Best regards,
Mike
i have spoken to a few friends about this, and i want to help raise money by visiting as many London underground station's as possible and getting a donation of a set amount for each station we visit/pass through
i don't know if anyone would like to help me organize this, but it would be a great help and i find Wikipedia and Wikimedia an invaluable source of information for me with help with my coursework
if you want to contact me, email me on either:
benleveque_1(a)hotmail.com
benleveque1(a)hotmail.com
benleveque(a)hotmail.co.uk
or
why_the-long_face(a)hotmail.co.uk
thanks =D
On 19 Nov 09, at 13:34, mediawiki-l-request(a)lists.wikimedia.org wrote:
> From: Platonides <Platonides(a)gmail.com>
>
> Jan Steinman wrote:
>>> From: "K. Peachey" <p858snake(a)yahoo.com.au>
>>>
>>> On Thu, Nov 19, 2009 at 11:00 AM, Jan Steinman <Jan(a)bytesmiths.com>
>>> wrote:
>>> Are you using any sort of cahceing, because that would just plain
>>> break it?
>>
>> No caching that I'm aware of beyond what MW does.
>>
>>
>> :::: The Earth isn't a pizza. You can't dial up and have one
>> delivered! -- Alf ::::
>> :::: Jan Steinman <http://www.EcoReality.org> ::::
>
> $wgUser->isLoggedIn() / $wgUser->getId()
>
> Default mediawiki caching will give you problems. You need to disable
> page caching on at least the pages which use your tag, by using
> $parser->disableCache()
> http://www.mediawiki.org/wiki/Extensions_FAQ#Recent_versions
Thanks, Platonides.
I do understand how to get the user from within PHP; I was hoping to
get it from within wikitext.
I suppose I could write an extension that does nothing but answer the
current user and their ID...
:::: Once a nation parts with the control of its curency and credit,
it matters not who makes that nation's laws. — Mackenzie King ::::
:::: Jan Steinman, EcoReality <http://www.EcoReality.org> ::::
I can't make my company use mediawiki inside its big intranet.
I saw http://www.mediawiki.org/wiki/Sites_using_MediaWiki/corporate link.
There is any company that give enterprise support for mediawiki?
By now confluence could be the solution, but I don't like it because
of sure problems (in the future) with the compliance to mediawiki.
--
www.opensurf.it
Hi all,
I've created a custom skin, based on Vector, for my website. I'd like
to replace the vector-action-, vector-namespace-, and vector-view-
system message variables with those tailored for my skin. How would I
go about setting the default for these, and then including them in
Special:AllMessages?
Jesse
http://www.wikieducator.org/User:Jesse_Groppihttp://www.jessewald.net
> From: "K. Peachey" <p858snake(a)yahoo.com.au>
>
> On Thu, Nov 19, 2009 at 11:00 AM, Jan Steinman <Jan(a)bytesmiths.com>
> wrote:
>>
> Are you using any sort of cahceing, because that would just plain
> break it?
No caching that I'm aware of beyond what MW does.
:::: The Earth isn't a pizza. You can't dial up and have one
delivered! -- Alf ::::
:::: Jan Steinman <http://www.EcoReality.org> ::::