[pmwiki-users] Translation downloads updated

Petko Yotov 5ko at 5ko.fr
Thu Feb 5 18:02:30 CST 2009

On Thursday 05 February 2009 20:19:22 Oliver Betz wrote:
> Petko Yotov wrote:
> (how http://www.pmwiki.org/wiki/PmWiki/ pages get into the
> distribution)
> >The script reports if the page in wiki.d has been modified, can display
> > and let me edit the latest version in wiki-markup (I didn't get that last
> > time), and update or revert the version in wikilib.d. Then it can update
> > the repo.
> You mean "wikilib.d in the repo"? Or does pmwiki.org use a wikilib.d?

Yes. Yes, and it is synchronized with the wikilib.d in the SVN repo.

> For compare and merge, I prefer a side by side method. There are lots
> of sophisticated tools out there - Beyond Compare, EC Merge, KDiff3,

Thanks, I'll check them out.

> Sadly these tools are not good to compare PmWiki page files. I already
> thought about making a bidirectional filter to convert a page file to
> a "comparable" format (with line breaks), but I didn't proceed because
> keeping the history was too complicated for me. Maybe I do it only for
> the current revision and drop the history on saving.

We don't need the page history, it is removed from the files that go in the 
release archive anyway. So, we need to check the difference between the 
previous trusted version (in wikilib.d) and the current version, and possibly 
fix the new or revert to the old version.

And it is not rocket science to replace all "%0a" with new lines, in order to 
make the text more human-friendly.

> >[1] I can use some help. If people from the community have the time and
> > are willing to help out, we could review all PmWiki/* pages and fix them
> > with an edit summary like "Ok for a release". This will be much faster.
> > (Other ideas are welcome too.)
> IMO a page text variable containing the documentation status as in the
> PmWikiDe pages is a good thing because they enable the use of
> pagelists.

An inexperienced author could break a page without removing the text variable. 
The page will need fixing, but the pagelist will not show it.

OTOH, a pagelist can display the last edit summary with 
{=$LastModifiedSummary}, that's why I first thought of it.

> In addition, I suggest a page where issues with the PmWiki/
> documentation shall be stored.

Why? I suggest issues to be immediately fixed in the Doc pages, unless there 
are questions or propositions for improvements. But in this case, we should 
apply the "Be bold in improving pages" principle, common for all wiki 

I just realised that we could add in *.PageActions links to *-Talk pages to 
all documentation pages, and we could discuss there the improvements of every 
such page. (Similar to Wikipedia's talk pages.) We could move there the 
non-answered FAQs and have an acceptable state of the main Doc page.

What do you think?

> Where do you suggest a discussion should take place - in this list
> (which I would prefer) or in PmWiki?

Me too, I slightly prefer the mailing list, but I also watch the recent 
changes on the wiki. And if we implement the *-Talk pages, the wiki will be 
more efficient.

Thanks a lot for your questions and suggestions!


More information about the pmwiki-users mailing list