Jump to content

Talk:Wiki software: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
Dsouzae (talk | contribs)
don't erase threads
 
(17 intermediate revisions by 10 users not shown)
Line 1: Line 1:
{{Talk header}}
{{Talk header}}
{{WikiProject banner shell|class=C|
{{WikiProjectBannerShell|1=
{{WikiProject Internet |class=c |importance=mid}}
{{WikiProject Internet |importance=mid}}
{{WikiProject Computing |class=c |importance=low |software=yes |software-importance=High}}
{{WikiProject Computing |importance=low |software=yes |software-importance=High}}
{{WikiProject Wikipedia |class=c |importance=high}}}}
{{WikiProject Wikipedia |importance=high}}
}}


== Case sensitivity ==
== Case sensitivity ==
Line 11: Line 12:


Was the reverse meant in the part I've bolded? That is, shouldn't that say "Case-'''in'''sensitivity on just the first letter"? On Wikipedia (and other MediaWiki sites), for example, <nowiki>[[</nowiki>[[wiki software]]<nowiki>]]</nowiki> automatically works as a link, but <nowiki>[[</nowiki>[[wIKI SOFTWARE]]<nowiki>]]</nowiki> does not. (<nowiki>[[</nowiki>[[Wiki Software]]<nowiki>]]</nowiki> only works because an explicit redirect was set up.) It'd help if the section had citations, too. &mdash;[[User:Undomelin|Undomelin]] ([[User talk:Undomelin|talk]]) 20:56, 7 May 2019 (UTC)
Was the reverse meant in the part I've bolded? That is, shouldn't that say "Case-'''in'''sensitivity on just the first letter"? On Wikipedia (and other MediaWiki sites), for example, <nowiki>[[</nowiki>[[wiki software]]<nowiki>]]</nowiki> automatically works as a link, but <nowiki>[[</nowiki>[[wIKI SOFTWARE]]<nowiki>]]</nowiki> does not. (<nowiki>[[</nowiki>[[Wiki Software]]<nowiki>]]</nowiki> only works because an explicit redirect was set up.) It'd help if the section had citations, too. &mdash;[[User:Undomelin|Undomelin]] ([[User talk:Undomelin|talk]]) 20:56, 7 May 2019 (UTC)

:Thanks for noticing that, you're quite right! I've gone ahead and [https://en.wikipedia.org/enwiki/w/index.php?title=Wiki_software&type=revision&diff=1088539428&oldid=1088183488 fixed it] --[[User:RProgrammer|RProgrammer]] ([[User talk:RProgrammer|talk]]) 17:02, 18 May 2022 (UTC)


== Is [[Confluence (software)]] a wiki? ==
== Is [[Confluence (software)]] a wiki? ==
Line 29: Line 32:


I myself (wwdada), had signed up my company to Confluence Cloud on the basis that we'd be receiving Wiki functionality. This is not as was expected from the name 'wiki' and it is important that other groups do not fall into this trap, without knowledge.
I myself (wwdada), had signed up my company to Confluence Cloud on the basis that we'd be receiving Wiki functionality. This is not as was expected from the name 'wiki' and it is important that other groups do not fall into this trap, without knowledge.

== What is the best way to rebuild corrupted Exchange server? ==

There is no doubt that third party tool are essential for successful Exchange server recovery. They play a most important role in making the organization profitable and for better enhancement. But tedious task is to find the best third party tool.

Before worry about finding best third party tool have look on what the Exchange server recovery software do.

Here is

Most of the time Exchange server got corrupted due to hardware issues, server failures, from user errors, dirty shutdown etc. So in order to access the damaged Exchange files Exchange server recovery software permits the Exchange user to repair the corrupted files and make them accessible in Outlook PST file.

Well you came to know that Exchange administrator has to choose the perfect third party software

The third party tool doesn’t mean anything if the Exchange administrator don’t find the better one. So everything depends on the better [https://www.edbmails.com/pages/exchange-server-recovery.html Exchange server recovery] tool. So the Exchange user can easily rebuild the corrupted Exchange server using EdbMails EDB to PST Converter. The software wants to help the user to find the solution for what they are looking

Now let’s talk about the some advanced feature of EdbMails EDB to PST Converter tool because feature is the only way to understand how truly effective the application can be

Here is the EdbMails EDB to PST Converter features

Exchange server recovery and migration
Restores the corrupted Exchange server
Saves the recovered Exchange to PST, EML, MHT, HTML and more
Exchange EDB recovery for free
Selective Exchange mailbox recovery
Recovery of Exchange server public folders
Recovers the single and multiple mailboxes
Permanently deleted mailbox recovery
Creates separate PST files for each recovered mailbox
Exchange server mailbox preview
Filter by Subject, From, To, Cc, Bcc, date based conditional filtering export
Attachments recovery
No dependency on Exchange server service and Active directory
Maintains the original folder hierarchy
Life time license validity with free upgrades
Exchange recovery operations report log files
Personalized live demo

Latest revision as of 03:31, 16 July 2024

Case sensitivity

[edit]

In the following portion:

By the time MediaWiki appeared, this convention had been largely abandoned in favor of explicitly marking links in edited source code with double square brackets. Page names thus did not interrupt the flow of English and could follow standard English capitalization convention. Case-sensitivity on the first letter but not subsequent letters supported standard English capitalization conventions and let writers author their pages in ordinary English, with the linking of particular words and phrases afterward. This proved to be the critical change that allowed ordinary authors of English to write wiki pages, and non-technical users to read them. This policy was extended to other natural languages, avoiding the use of unusual-looking text or awkward capitalization that violates the language's own rules.

Was the reverse meant in the part I've bolded? That is, shouldn't that say "Case-insensitivity on just the first letter"? On Wikipedia (and other MediaWiki sites), for example, [[wiki software]] automatically works as a link, but [[wIKI SOFTWARE]] does not. ([[Wiki Software]] only works because an explicit redirect was set up.) It'd help if the section had citations, too. —Undomelin (talk) 20:56, 7 May 2019 (UTC)[reply]

Thanks for noticing that, you're quite right! I've gone ahead and fixed it --RProgrammer (talk) 17:02, 18 May 2022 (UTC)[reply]

I'm seeing the beginning of a slow-motion edit war on this article between what looks like disgruntled Confluence (software) users and myself. We should stop this now.

On one side we have editors who believe that Confluence is no longer a wiki because it has abstracted away two features (wiki markup and what we would call the creation of a redlink as you are editing an article).

On my side are editors ... OK, so far just one editor, me ... who take a more ecumenical view of what a wiki is. I believe that the opening paragraph of the current version of Wiki is correct, and that "A wiki is a knowledge base website on which users collaboratively modify content and structure directly from the web browser." Confluence would continue to be that, even if it lost those two important features.

wwdada: For the record, I am also a Confluence user of an older version that still has those features. When I have upgraded to the current version and lost those features, I will also be upset, but Confluence will still be a wiki. Vadder (talk) 18:45, 31 October 2019 (UTC)[reply]

Hi, I don't think people should take up Confluence at this stage thinking it is a Wiki. Confluence also (despite their size) do not own the definition of Wiki The most essential functionality is the ability to make a link like this to "[Wiki Properties]" or "[Newly discovered Planet]" or "[New Products]". Many in the comment chain on that issue have also indicated that without this functionality, (and especially with NO wikiMarkup), Confluence is no longer a Wiki (no longer a Quick mechnism for typing linked documents, as originally formulated). No Alternative vision has been put forward, just a web-editing applet. https://jira.atlassian.com/browse/CONFCLOUD-67129

I myself (wwdada), had signed up my company to Confluence Cloud on the basis that we'd be receiving Wiki functionality. This is not as was expected from the name 'wiki' and it is important that other groups do not fall into this trap, without knowledge.