Welcome to TiddlyWiki created by Jeremy Ruston, Copyright © 2007 UnaMesa Association
Without his exceptional skill and adeptness at translation and interpretation, our communication and coordination with our Russian Federation counterparts would have been impossible.
<html><div align="right">(<i>Capt. L. E. Olsen, Senior Analyst, USN</i>)</div></html>
Mr. Lane provided timely, precise, and very efficient interpretation support. The use of both languages was crisp and effective, with excellent preservation of meaning, as well as emotional, content, idiomatic, and technical nuances. Many thanks from the group.
<html><div align="right">(<i>A. Sargasyan, International Space Station Medical Team</i>)</div></html>
<html>
<br style="font-weight: bold;" />
<table width="60%" cellspacing="1" cellpadding="1" border="1" align="" summary="">
<caption style="font-weight: bold;">ATV Abbreviations</caption>
<tbody>
<tr>
<th><a href="#" id="memorizeLink" onclick="return Mem.start( this )">Abbreviation</a><br /> </th>
<th><a href="#" id="memorizeLink" onclick="return Mem.start( this )">Term</a><br /></th>
</tr><tr><td>MVM</td><td>mission vehicle management</td></tr>
<tr><td>CMS</td><td>communication monitoring system</td></tr>
<tr><td>MSU</td><td>monitoring and safing unit</td></tr>
<tr><td>DPS</td><td>data processing system</td></tr>
<tr><td>RDS</td><td>Russian docking system</td></tr>
<tr><td>GMS</td><td>GNC measurement system</td></tr>
<tr><td>FAS</td><td>flight application software</td></tr>
<tr><td>PWS</td><td>power system</td></tr>
<tr><td>PRO</td><td>propulsion system</td></tr>
<tr><td>DRS</td><td>docking and refueling system</td></tr>
<tr><td>TCC</td><td>thermal control system</td></tr>
<tr><td>FCM</td><td>flight control monitoring</td></tr>
<tr><td>PDE</td><td>propulsion drive electronics</td></tr>
<tr><td>FUM</td><td>functional unit module</td></tr>
<tr><td>STR</td><td>star tracker</td></tr>
<tr><td>RECS</td><td>Russian electronics control set (Russian electronics inside ATV)</td></tr>
<tr><td>TGM</td><td>telegoneometer</td></tr>
<tr><td>VDM</td><td>videometer</td></tr>
<tr><td>ACCA</td><td>accelerometer assembly</td></tr></tr>
</tbody>
</table>
</html>
* Galexi Wordsmiths, LLC offers translation services primarily from Russian into English (though we do have an affiliate who does fine work from English into Russian). We do interpretation as well, and have worked in places from Billings to Baikonur. We have offices in Colorado and Texas, but nearly all work is currently being done out of our Houston office.
* We strive to produce translations that read as if a literate native speaker had written the document.
* If you're looking for really cheap translation, you're in the wrong place. We don't charge as much as most agencies – after all, we haven't the overhead – but we also don't work for rates that all but guarantee a poor machine-quality translation.
* We can recommend translators to/from other languages, or subcontract them if you like. (Frankly, though, we take the quality of our product seriously, so subcontracting isn't cheap.)
{{{
Adaptor.close()
}}}
Should only be called after the last callback has completed
Closes an adaptor, severing the connection to the workspace and host (see ServerAdaptorConcepts).
* [[Adaptor.close]] shouldn't be called while there are outstanding callbacks
* [[Adaptor.close]] must be called to ensure that all pending write operations are completed
''Parameters:''
None.
''Returns:''
|true |on success |
|string |an error message if there was an error issuing the request |
{{{
Adaptor.getTiddler(title,context,userParams,callback)
}}}
Retrieves a named tiddler from an adaptor opened to a workspace on a host (see ServerAdaptorConcepts). This function uses the AsynchronousPattern.
''Parameters:''
|title |Title of the tiddler to retrieve |
|context |context object that is passed to the callback function |
|userParams |user settable object object that is passed on unchanged to the callback function |
|callback |Reference to callback function, see AdaptorCallbackSignature |
''Returns:''
|true |on success |
|string |an error message if there was an error issuing the request |
''Callback signature'' as per AdaptorCallbackSignature with additional fields:
|context.tiddler |The retrieved tiddler object, with all the standard fields and the ServerAdaptorExtendedFields filled in |
{{{
Adaptor.getTiddlerList(context,userParams,callback,filter)
}}}
Gets a list of the tiddlers available on an adaptor opened to a workspace on a host (see ServerAdaptorConcepts). This function uses the AsynchronousPattern.
''Parameters:''
|context |context object that is passed to the callback function |
|userParams |user settable object object that is passed on unchanged to the callback function |
|callback |reference to callback function, see AdaptorCallbackSignature |
|filter |optional string to select tiddlers returned in list, see TiddlerSelection |
''Returns:''
|true |on success |
|string |an error message if there was an error issuing the request |
''Callback signature'' as per AdaptorCallbackSignature with additional fields:
|context.tiddlers |Array of tiddlers, with a minimum set of fields filled in, see below |
The tiddlers in the {{{context.tiddlers}}} array have the following minimum set of fields, although particular adaptors may choose to return additional information in further fields.
|title |Title of the tiddler (as used in [[Adaptor.getTiddler]]) |
{{{
Adaptor.getWorkspaceList(context,userParams,callback)
}}}
Gets a list of the workspaces available on a particular host (see ServerAdaptorConcepts). This function uses the AsynchronousPattern.
''Parameters:''
|context |context object that is passed to the callback function |
|userParams |user settable object object that is passed on unchanged to the callback function |
|callback |Reference to callback function, see AdaptorCallbackSignature |
''Returns:''
|true |on success |
|string |an error message if there was an error issuing the request |
''Callback signature'' as per AdaptorCallbackSignature with additional fields:
|context.workspaces |An array of information about each available workspace (see below) |
The entries in the {{{context.workspaces}}} array have the following minimum set of fields, although particular adaptors may choose to return additional information in further fields.
|title |Title of the workspace (as used in [[Adaptor.openWorkspace]]) |
{{{
Adaptor.openHost(host,context,userParams,callback)
}}}
Creates an adaptor for talking to a particular host (see ServerAdaptorConcepts). This function uses the AsynchronousPattern.
''Parameters:''
|host |URI of server |
|context |context object that is passed to the callback function |
|userParams |user settable object object that is passed on unchanged to the callback function |
|callback |Reference to callback function, see AdaptorCallbackSignature |
''Returns:''
|true |on success |
|string |an error message if there was an error issuing the request |
''Callback signature'' as per AdaptorCallbackSignature.
{{{
Adaptor.openWorkspace(host,context,userParams,callback)
}}}
Opens a particular workspace in an adaptor that has already been opened on a host (see ServerAdaptorConcepts). This function uses the AsynchronousPattern.
''Parameters:''
|workspace |Name of workspace |
|context |context object that is passed to the callback function |
|userParams |user settable object object that is passed on unchanged to the callback function |
|callback |Reference to callback function, see AdaptorCallbackSignature |
''Returns:''
|true |on success |
|string |an error message if there was an error issuing the request |
''Callback signature'' as per AdaptorCallbackSignature.
{{{
Adaptor.putTiddler(tiddler,context,userParams,callback)
}}}
Stores a named tiddler to an adaptor opened to a workspace on a host (see ServerAdaptorConcepts). This function uses the AsynchronousPattern.
''Parameters:''
|tiddler |The Tiddler to store |
|context |context object that is passed to the callback function |
|userParams |user settable object object that is passed on unchanged to the callback function |
|callback |Reference to callback function, see AdaptorCallbackSignature |
''Returns:''
|true |on success |
|string |an error message if there was an error issuing the request |
''Callback signature'' as per AdaptorCallbackSignature.
{{{
callback(context,userParams)
}}}
|userParams |userParams object (unchanged) as passed by the original caller |
context contains the following fields:
|context.status |True if original call was successful, false if there was an error |
|context.statusText |Error message if context.status is false |
|context.adpator |Reference to the adaptor object |
Additionally, context may contain the following fields, depending on the adaptor function originally called:
|context.workspaces |Array of workspaces, see [[Adaptor.getWorkspaceList]] |
|context.tiddler |Tiddler retrieved, see [[Adaptor.getTiddler]]|
|context.tiddlers |Array of Tiddlers retrieved, not all Tiddler fields filled in, see [[Adaptor.getTiddlerList]]|
|context.revisions |Array of revisions of the current Tiddler, not all Tiddler fields filled in, see [[Adaptor.getTiddlerRevisionList]] |
Aerospace is, perhaps, the subject area in which the company has the most experience. The company's lead interpreter and translator, [[Alex Lane]] has been translating Russian aerospace documents into English for more than a dozen years, during which time he worked for a NASA prime contractor for five years to closely support the joint ~US-Russian space program.
!!Career overview
Thirty years of professional experience, including 9 years in mechanical, electrical, and process control engineering and 4 years in software development, product management, marketing, and consulting. Mr. Lane has worked full time in the translation and interpretation industry as a translator, interpreter, and manager for the past 17 years. His translation career began in 1978, on a freelance basis. He is currently the lead interpreter and translator at Galexi Wordsmiths, LLC.
!!Translation & Interpretation Experience
Spoken Russian is fluent, with near-native pronunciation. Experienced escort, consecutive, and simultaneous interpreter. Certified by the American Translators Association to translate from Russian into English. Considerable experience as a writer and editor of English text. Translation productivity generally exceeds 500 words per hour.
!!Areas of expertise
Based on education, work experience, and/or completion of a large volume of translation, Mr. Lane is particularly qualified to accept assignments dealing with the following [[subjects|Subject Areas]]:
* aerospace and related fields,
* control systems,
* petrochemical, oil, gas and related fields,
* engineering specifications,
* safety assurance,
* nuclear technology,
* nuclear disarmament,
* computers, networking, programming and related subjects,
* general technical subjects, and
* military topics.
Rename this tiddler to 'ColorPalette' to enable this color scheme
Background: #ffc
Foreground: #000
PrimaryPale: #fc8
PrimaryLight: #f81
PrimaryMid: #b40
PrimaryDark: #410
SecondaryPale: #ffc
SecondaryLight: #fe8
SecondaryMid: #db4
SecondaryDark: #841
TertiaryPale: #e88
TertiaryLight: #c66
TertiaryMid: #944
TertiaryDark: #633
This tiddler shows some more complex effects that can be obtained with cunning use of CSS. Not all of these will work properly on all browsers because of differences in CSS implementation, but they should fail gracefully.
You can have special formatting for a specific, named tiddler like this:
{{{
#tiddlerHelloThere .title {
background-color: #99aaee;
}
}}}
Or for the first displayed tiddler:
{{{
div.tiddler:first-child .title {
font-size: 28pt;
}
}}}
Or just for the first line of every tiddler:
{{{
.viewer:first-line {
background-color: #999999;
}
}}}
Or just for the first letter of every tiddler:
{{{
.viewer:first-letter {
float: left;
font-size: 28pt;
font-weight: bold;
}
}}}
Or just for tiddlers tagged with a particular tag (note that this won't work for tags that contain spaces):
{{{
div[tags~="welcome"].tiddler .viewer {
background-color: #ffccaa;
}
div[tags~="features"].tiddler .viewer {
background-color: #88aaff;
}
}}}
Благодаря изобретению солнечного магнитографа удалось измерить напряженность слабого фонового магнитного поля Солнца и впоследствии обнаружить обращение полярности этого поля в моменты максимума процесса пятнообразования. Вначале были измерены только относительно сильные магнитные поля крупного масштаба, и поэтому они казались изолированными структурами, окруженными областями “нулевого” поля, вследствие чего из назвали униполярными магнитными областями, в то время как активные области (АО) были названы биполярными областями. Считалось, что униполярные магнитные поля образуются путем дисперсии магнитных полей АО, что нашло отражение в эволюционной модели Бэбкока–Лэйтона. В их интерпретации новый магнитный поток всплывает из-под фотосферных слоев в виде АО на низких гелиографических широтах и затем распространяется от них к высоким широтам благодаря проциссу перераспределении магнитного потока случайными движениями силовых линий и меридиональной циркуляции под влиянием шира дифференциального вращения Солнца.
The invention of the solar magnetograph has made it possible to measure the intensity of the weak background solar magnetic field and subsequently, to detect that field’s polarity reversal during the peak of the sunspot-formation process. At first, only relatively strong, large-scale magnetic fields were measured, and these were called unipolar magnetic regions, as they appeared to be isolated structures surrounded by regions of “zero” field. At the same time, active regions (~ARs) were called bipolar regions. Unipolar magnetic fields were believed to be formed by the dispersal of AR magnetic fields, which was reflected in the Babcock–Leighton evolutionary model. In their interpretation, new magnetic flux wells up from below the photospheric layers in the form of ~ARs at low heliographic latitudes and then propagates from them toward high latitudes by virtue of magnetic flux redistribution caused by the random motion of field lines and meridional circulation brought about by shear due to solar differential rotation.
Asynchronous methods are used by the low level HttpFunctions, and by higher level mechanisms such as the ServerAdaptorMechanism.
The standard TiddlyWiki approach is illustrated with this example of a {{{procrastinate()}}} function that takes a string parameter which is then returned after 1 second by a callback function:
{{{
// Call an asynchronous function
function test()
{
// The context object is for storing information that you're going to need inside the callback function
var myContext = {
param1: "a string",
param2: {an: "object"},
param3: ["an","array"}
};
// Call the function including a reference to the callback function and it's context
procrastinate("hello tomorrow's world",myCallback,myContext);
}
// The callback function that gets invoked after 1 second
function myCallback(status,context,procrastinatedString)
{
displayMessage("Message from the past: " + procrastinatedString);
displayMessage("Message context: " + context.param1);
}
// The procrastinate function invokes a callback after 1 second with a specified string parameter
// procrastinatedString - the string to pass back to the callback function
// callback - the callback function
// context - a context object that is passed to the callback function
// Returns true if the request was issued or a string error message if it failed
function procrastinate(procrastinatedString,callback,context)
{
window.setInterval(callback,1000,true,context,procrastinatedString);
}
}}}
Asynchronous programming is necessary in several situations but is full of pitfalls for the unwary:
* On many browsers, {{{alert()}}} doesn't work reliably in some asynchronous callbacks
* It's very easy to miss errors by ignoring callback returns
If you check this box in the InterfaceOptions, TiddlyWiki will automatically SaveChanges every time you edit a tiddler. In that way there's a lot less chance of you losing any information.
However, if you also have the SaveBackups checkbox ticked, you'll end up with a lot of archived files. You may prefer to select either one or the other.
<html><hr><center><a href="http://backpackit.com/?referrer=BPHBNLJ"><img border="0" title="Backpack: Get Organized and Collaborate" alt="Backpack: Get Organized and Collaborate" src="http://123.backpackit.com/images/backpack11230.gif" width="112" height="30" /></a></center><hr></html>
One of the great strengths of TiddlyWiki is the way that its interface can be customised by editting various shadow tiddlers. However, a problem that has consistently emerged is the difficulty of reconciling the needs of authors, who need access to the full array of TiddlyWiki features, and the needs of ordinary readers, who generally benefit from seeing a restricted set of functionality more suited to their needs.
The new backstage area in release 2.2 offers a solution to this conundrum by providing a consistent way of accessing authoring functionality that is independent of the interface customisations (so, even if you blast away the contents of your PageTemplate, you can still access the backstage area).
The backstage area is only available when a TiddlyWiki is edittable - typically meaning that it's been opened off of a {{{file://}}} URL. It appears as an unobtrusive link in the topright corner of the page. Clicking it reveals the backstage toolbar consisting of commands like {{{saveChanges}}} and drop-down tasks like ImportTiddlers, SyncMacro, PluginManager and Tweak (which provides access to the new OptionsMacro).
|''URL:''|http://tiddlywiki.bidix.info/|
|''Description:''|Repository for BidiX's TiddlyWiki Extensions|
|''Author:''|BidiX|
To make quoted bits of text stand out, you can use BlockQuotes within your [[tiddler]]s, like this:
JeremyRuston said:
<<<
A TiddlyWiki is like a blog because it's divided up into neat little chunks, but it encourages you to read it by hyperlinking rather than sequentially: if you like, a non-linear blog analogue that binds the individual microcontent items into a cohesive whole.
<<<
Like BulletPoints and NumberedBulletPoints, you can have multiple levels of BlockQuotes. Just edit this tiddler to see how it's done.
>level 1
>level 1
>>level 2
>>level 2
>>>level 3
>>>level 3
>>level 2
>level 1
|''URL:''|http://bob.mcelrath.org/plugins.html|
|''Description:''|Bob McElrath's Plugins|
|''Author:''|BobMcElrath|
Creating BulletPoints is simple.
* Just add an asterisk
* at the beginning of a line.
** If you want to create sub-bullets
** start the line with two asterisks
*** And if you want yet another level
*** use three asterisks
* Edit this tiddler to see how it's done
* You can also do NumberedBulletPoints
The Mozilla-based [[Camino browser|http://www.caminobrowser.org/]] on Macintosh OS X works well with TiddlyWiki, including the ability to SaveChanges.
Abandons any pending edits to the current tiddler, and switches it the default view. It is used with the ToolbarMacro like this:
{{{
<<toolbar cancelTiddler>>
}}}
When you upload a TiddlyWiki to a web server, if doesn't load properly, it may be a CharacterEncoding issue.
TiddlyWiki uses Unicode ~UTF-8 encoding and won't load properly if your host is serving it as ~ISO-8859-1. You should be able to check this by loading another page on the server in FireFox and selecting 'Page Info' on the 'Tools' menu.
If this is the case, it should be reasonably easy to sort out. We recommend that you contact your server host and ask them to serve it in ~UTF-8 mode. If you are more technically hands-on, you may be able to [[solve the issue yourself|http://www.w3.org/International/questions/qa-htaccess-charset]].
Closes all other open tiddlers, except for any that are being editted. It is used with the ToolbarMacro like this:
{{{
<<toolbar closeOthers>>
}}}
Closes the current tiddler, regardless of whether it is being editted. It is used with the ToolbarMacro like this:
{{{
<<toolbar closeTiddler>>
}}}
[>img[tiddlywiki.org logo|http://trac.tiddlywiki.org/chrome/site/tworg_logo_med.jpg][http://www.tiddlywiki.org]]TiddlyWiki today is the result of the efforts of dozens of people around the world generously contributing their time and skill. The core of the TiddlyWiki development community is http://www.tiddlywiki.org. It hosts the master copy of the TiddlyWiki source code, and a system for tracking bugs and enhancement requests. The community welcomes [[contributions|Contribute]].
There are two GoogleGroups for discussions about TiddlyWiki. They are the best places to ask questions about TiddlyWIki, and to connect with other enthusiasts:
* A TiddlyWiki group for general discussion, bug reports and announcements at http://groups.google.com/group/TiddlyWiki
* A TiddlyWikiDev group for discussion about TiddlyWiki development at http://groups.google.com/group/TiddlyWikiDev
For non-English language speakers,
* TiddlyWikiFR, in French, at http://groups.google.com/group/TiddlyWikiFR
* TiddlyWiki 華語支援論壇, in Chinese, at http://groups.google.com/group/TiddlyWiki-zh
* TiddlyWikiPT, in Brazilian Portuguese, at http://groups.google.com.br/group/tiddlywikipt
<html>
<a href="http://www.frappr.com/tiddlywiki"><img src="http://www.frappr.com/i/frapper_sticker.gif" border="0" alt="Check out our Frappr!" title="Check out our Frappr!"></a>
</html>
TiddlyWiki is legally owned by [[The UnaMesa Foundation|http://www.unamesa.org/]].
PageTemplate
|>|>|SiteTitle - SiteSubtitle|
|MainMenu|DefaultTiddlers<<br>><<br>><<br>><<br>>ViewTemplate<<br>><<br>>EditTemplate|SideBarOptions|
|~|~|OptionsPanel|
|~|~|AdvancedOptions|
|~|~|<<tiddler Configuration.SideBarTabs>>|
''StyleSheet:'' StyleSheetColors - StyleSheetLayout - StyleSheetPrint
SiteUrl
SideBarTabs
|[[Timeline|TabTimeline]]|[[All|TabAll]]|[[Tags|TabTags]]|>|>|[[More|TabMore]] |
|>|>||[[Missing|TabMoreMissing]]|[[Orphans|TabMoreOrphans]]|[[Shadowed|TabMoreShadowed]]|
|voice:|+1 (713) 898-8918|
|eFax:|+1 (719) 623-0547|
|email:|words@galexi.com|
Call if you need our mailing address.
TiddlyWiki has an enthusiastic and friendly [[Community]] of people around the world helping to grow and improve it. But there's always more to do and we welcome any offers of assistance. There are many ways that you can help:
* Testing and [[reporting bugs|http://trac.tiddlywiki.org/wiki/ReportingBugs]] against the core code. Clear, easily reproducible bug reports are incredibly useful and really help the team improve the quality of TiddlyWiki
* [[Contributing code|http://trac.tiddlywiki.org/wiki/ContributingCode]]
* [[Making translations|http://trac.tiddlywiki.org/wiki/Translations]]
* Documentation needs planning, writing and editting:
** User guide information at http://tiddlywikiguides.org/
You can wrap any text in an HTML {{{<span>}}} or {{{<div>}}} with a specified CSS class. This allows custom CSS styling in a nice, modular way. By placing a rule in your StyleSheet tiddler like {{{.wrappingClass{color: #666; background: #bbb} }}} you can markup a piece of text in the tiddler using this code:
{{{
{{wrappingClass{Text that is now accentuated}}}
}}}
{{wrappingClass{Text that is now accentuated}}}
By default, the text is placed in a {{{<span>}}}. To use a {{{<div>}}} instead, insert a line break before the text:
{{{
{{wrappingClass{
Text that is now accentuated}}}
}}}
{{wrappingClass{
Text that is now accentuated}}}
Sometimes it's necessary to include custom HTML markup in the {{{<head>}}} of a TiddlyWiki file - typically for compatibility with ad serving software, external libraries, or for custom meta tags. The CustomMarkup operation defines four shadow tiddlers whose contents are spliced into the saved HTML file. (If you do a view/source you'll see the markers referred to below).
|!Title |!Location |!Marker |
|MarkupPreHead |Start of the {{{<head>}}} section |{{{<!--PRE-HEAD-START-->}}} |
|MarkupPostHead |End of the {{{<head>}}} section |{{{<!--POST-HEAD-START-->}}} |
|MarkupPreBody |Start of the {{{<body>}}} section |{{{<!--PRE-BODY-START-->}}} |
|MarkupPostBody |End of the {{{<body>}}} section |{{{<!--POST-BODY-START-->}}} |
MarkupPreHead is the only one with shadow content: a link to the default location of the RSS feed.
Starting with this revision, you can skin TiddlyWiki with a special StyleSheet tiddler containing your own CSS style sheet declarations. Unlike hacking the HTML directly, the StyleSheet tiddler withstands upgrading to a new version of the TiddlyWiki code (see HowToUpgrade). You can also use the NestedStyleSheets feature to structure your CSS declarations.
The ExampleStyleSheet shows some of the basic options you can control (see AnotherExampleStyleSheet for more complex examples). SaveChanges and then click refresh in your browser to see StyleSheet changes. Any errors in your CSS syntax will be caught and displayed, but they shouldn't stop TiddlyWiki from working.
You can customise the appearance and behaviour of TiddlyWiki to almost any degree you want:
* Use the ColorPalette to change the basic colour scheme
* Create a CustomStyleSheet for finer grained control over the appearance
* Customise the PageTemplate, ViewTemplate or EditTemplate to change the composition of the page and the layout of individual tiddlers
* Use off-the-shelf themes from [[TiddlyThemes|http://tiddlythemes.com/]]
* Visit the [[Configuration]] summary to see all the special configuration tiddlers
* Install [[Plugins]] to extend the core functionality (and you can also easily [[write or adapt your own|http://gimcrackd.com/etc/src/codex/]])
There are also a bunch of TiddlyWikiTools that you can use to enhance TiddlyWiki.
Several [[Macros]] including the TodayMacro take a DateFormatString as an optional argument. This string can be a combination of ordinary text, with some special characters that get substituted by parts of the date:
* {{{DDD}}} - day of week in full (eg, "Monday")
* {{{ddd}}} - short day of week (eg, "Mon")
* {{{DD}}} - day of month
* {{{0DD}}} - adds a leading zero
* {{{DDth}}} - adds a suffix
* {{{WW}}} - ISO-8601 week number of year
* {{{0WW}}} - adds a leading zero
* {{{MMM}}} - month in full (eg, "July")
* {{{mmm}}} - short month (eg, "Jul")
* {{{MM}}} - month number
* {{{0MM}}} - adds leading zero
* {{{YYYY}}} - full year
* {{{YY}}} - two digit year
* {{{wYYYY}}} - full year with respect to week number
* {{{wYY}}} two digit year with respect to week number
* {{{hh}}} - hours
* {{{0hh}}} - adds a leading zero
* {{{hh12}}} - hours in 12 hour clock
* {{{0hh12}}} - hours in 12 hour clock with leading zero
* {{{mm}}} - minutes
* {{{0mm}}} - minutes with leading zero
* {{{ss}}} - seconds
* {{{0ss}}} - seconds with leading zero
* {{{am}}} or {{{pm}}} - lower case AM/PM indicator
* {{{AM}}} or {{{PM}}} - upper case AM/PM indicator
[[Welcome, Visitor!]] [[Site News]]
Deletes the current tiddler. A confirmation dialogue is displayed unless disabled with the ConfirmBeforeDeleting checkbox in AdvancedOptions. It is used with the ToolbarMacro like this:
{{{
<<toolbar deleteTiddler>>
}}}
Gleaned from ''ГОСТ 27.002-83, Надежность в технике'' (Engineering Dependability). (My edits to terms are shown //in italics///kom; comments are entirely my own.)
|!''Russian''|!''English''|!''French''|!''Comments''|h
|надежность|dependability|fiabilité|"Надежность" is often rendered as "reliability," distinguishing "dependability" as "функциональная надежность." The standard itself notes that "[надежность] is a complex property that, depending on the purpose of an item and the conditions in which it is used, is a combination of [безотказности], [долговечности], [ремонтопригодности], and [сохраняемости]."|
|безотказность|reliability|bon fonctionnement|
|долговечность|longevity|durabilité|
|ремонтопригодность|maintainability|maintenabilité|
|сохраняемость|storageability|aptitude au stockage; conservabilité|
|исправное состояние; исправность|state of operability; //operable//|bon état|
|неисправное состояние; неисправность|state of nonoperability; //inoperable//; //failed//|mauvais état|
|работоспособное состояние; работоспособность|state of serviceability|état opérationnel|
|неработоспособное состояние; неработоспособность|state of nonserviceability|état non opérationnel|
|предельное состояние|marginal state|état limite|
|критерий предельного состояние|marginal state criterion|critère d'état limite|
|дефект|defect|défaut|
|повреждение|damage|endommagement|
|отказ|failure|défaillance|
|критерий отказа|failure criterion|critère de défaillance|
|техническое обслуживание|maintenance|maintenance|
|восстановление работоспособного состояния; восстановление|restoration|remise en état|
|ремонт|repair|réparation|
|восстанавливаемый объект|restorable item|dispositif restituable|
|невосстанавливаемый объект|nonrestorable item|dispositif non restituable|
|ремонтируемый объект|repairable item|dispositif réparable|
|неремонтируемый объект|nonrepairable item|dispositif non réparable|
|показатель надежности|reliability index|caractéristique de fiabilité|
|единичный показатель надежности|simple reliability index|caractéristique simple de fiabilité|
|комплексный показатель надежности|integrated reliability index|caractéristique composite de fiabilité|
|наработка|operating time|dureé de fonctionnement|
|наработка до отказа|time to failure|dureé avant défaillance|
|наработка между отказами|time between failures|dureé entre défaillances|
|технический ресурс; ресурс|//operating lifetime//|dureé cumuleé (de fonctionnement)|
|срок службы|//(service)// lifetime|dureé de vie|
|срок сохраняемости|storageability time|dureé de conservabilité (aptitude au stockage)|
|время восстановление работоспособного состояния; время восстановления|restoration time|temps de remise en état|
Because TiddlyWiki is a single HTML file, you've actually already downloaded the entire software just by viewing this site. If you want to be able to SaveChanges, you can save your own blank TiddlyWiki to your local drive by right clicking on [[this link to empty.html|empty.html]] and selecting 'Save link as...' or 'Save target as...'. You can choose where to save the file, and what to call it (but make sure that it's saved in HTML format and with an HTML extension).
@@There can be confusing and subtle differences between different browsers. Some points to watch:@@
* If you're using Windows XP Service Pack 2 or Windows Vista, check for known ServicePack2Problems and VistaIssues
* Do ''not'' use the File/Save command in your browser to save TiddlyWiki, because of SaveUnpredictabilities.
* Make sure that you're saving in HTML (or "page source" format), not one of the new-fangled archive formats
If you're already using TiddlyWiki, see HowToUpgrade. If you want to save a complete copy of this site, including all the instructions and other text, you can use this [[this link|index.html]].
Try holding down the alt- or shift-key while clicking on a link to a tiddler, on the 'options' button or on the CloseButton for a tiddler. Kind of a respectful homage to Mac OS X, which does something similar for many of its system animations. (On browsers like InternetExplorer that use the shift key to open a new window, it's best to use the alt-key).
Switches the current tiddler to the current edit view. It is used with the ToolbarMacro like this:
{{{
<<toolbar editTiddler>>
}}}
|Compiled by:|M. Rosenberg and S. Bobryakov|
|Publisher:|Elsevier|
|Publication date:|2003 (hardcover, two volumes)|
|Number of pages:|732 (~Russian-English); 936 (~English-Russian)|
|~ISBNs:|0444510311 (for the set of both dictionaries); 0444510312 (~Russian-English); 0444510314 (~English-Russian)|
|List Price:|$325 (for the set of both volumes)|
<<<
''Reviewed by Alex Lane'' Originally published in the August 2004 issue of //The ATA Chronicle//. Reprinted with permission.
<<<
Soon after receiving the //Dictionary of Nuclear Engineering,// I began to review it and found myself behaving like a faulty old-fashioned vinyl record that gets to a certain point and then skips back one groove, unable to move ahead (to the great consternation of my editor). You see, I wanted to //like// this book, for a variety of reasons (including my having worked with one of the coauthors, Milton Rosenberg, a few years ago), but various things about this book kept getting in the way. I did most of my review work with the Russian–English version of the dictionary. The English–Russian version appears to contain the same information, arranged in the “other” direction, naturally, plus a fairly extensive section at the end of the book with English abbreviations (which largely accounts for the 200-page greater size of the English–Russian volume).
Physically, the book is solid, has a nice heft, and is visually appealing. Inside, I found the display font to be a little on the small side, but certainly readable. A side benefit of the layout is that the pages have ample margins, which can be quite useful for penciling in additional terms, notes, or what have you. Personally, I also applaud the decision to print entire entries instead of reverting to the use of abbreviations or tildes to save space.
However, I found the large margin at the tops of the pages troublesome, as //there are no guide words.// Given that the headwords for entries and subentries are printed in the same bold font (though the latter are indented slightly) and that numerous subentries may exist for an entry (nearly 18 pages of them for "реактор"), the lack of guide words will, in my opinion, cause the reader to work harder to use the book. Since looking at the first entry on a page didn’t necessarily help with navigation, I ended up scanning columns, looking for unindented entries to help me figure out where I was.
If you open the book to page 588, for example, the first unindented entry ("стержневой") is near the bottom of the second column; how fast you get to it will depend on your visual acuity and scanning skills. The alternative is to read an entry or two at the top of the page and figure out the common term (e.g., on page 602: "стержевой твэл по состоянию на конец кампании" and "стержевой твэл с гранулированным топливом"). The experienced translator will make the connection easily, perhaps even after reading only the first entry. Less experienced translators may find the going a bit rougher.
I also found it difficult to get used to the arrangement of subentries. Under the main entry (I’ll use "реактор" as an example) is a list that starts with subentries (if any) that use the entry word as part of a phrase or idiom (in this case, "вне реактора" and "расположенный под реактором"). Then there follows an alphabetical list of entries that start with the entry word, followed by modifiers ("реактор атомной станции теплофикации," "реактор атомной теплоцентрали," and so on). Finally, there follows an alphabetical list of entries where the modifiers precede the entry word ("аварийный ядерный реактор," etc.).
The practical effect of this is having to keep in mind the possibility of looking things up in two places, and it not always being clear what the two places are. For example, if you are faced with looking up "реактор с тяжеловодным замедлителем" or "ядерный реактор с тяжеловодным замедлителем," you’re in luck, as both entries exist (albeit the latter is more extensive). If you are looking for "реактор типа GCR," however, you won’t find it among the "реактор типа xxx" entries (where xxx are reactor types), but will have to look under "ядерный реактор типа GCR."
There were times I was puzzled by the level of detail given for entries. For example, on page 321, "смотровое окно" offers an embarrassment of riches, with all of the over 20 alternatives being very similar variations, in my opinion, of “observation window.” At the other extreme, anyone looking up "одобрять" on the page opposite would do well to let their eye wander up one entry, as "одобрение" provides a richer choice than the lone “to approbate” given for the verb.
I also felt there to be an uncomfortably large number of simple word combinations scattered in among the advertised 50,000 entries. For example, I look at subentries such as "искуственный радионуклид" (under "радионуклид," p. 451) and wonder if anything other than “artificial radionuclide” will fit the bill. A large number of entries under "перенос" (page 366) also fall into this category, in my opinion.
Finally, as the title implies, the main emphasis of the terms in the book is engineering, which is not where the main thrust of nuclear activity is today (at least not in my experience, which has involved mostly disarmament-related themes). In my opinion, this places some inherent limitations on the usefulness of the dictionary.
In the end, between the missing guide words, the organization of subentries, and the presence of what I consider to be extraneous entries, I found that this dictionary requires the reader to expend of a lot more effort than I have become used to investing when using a paper dictionary, especially one with such a price tag.
|Compiled by:|B. Zhelyazova|
|Publisher:|Elsevier|
|Publication date:|2005 (hardcover)|
|No. of pages:|996 |
|ISBN:|044451533X|
|List price:|$165; €150; ₤103 |
<<<
''Reviewed by Alex Lane'' Originally published in the January 2006 issue of //The ATA Chronicle//. Reprinted with permission.
<<<
The marketing material for this tome describes the entries as being from the fields of "automation, technology of management and regulation, computing machine and data processing, computer control, automation of industry, laser technology, theory of information and theory of signals, theory of algorithms and programming, philosophical bases of cybernetics, cybernetics, and mathematical models." I found this to be a fairly aggressive agenda for a dictionary containing a jot less than 13,000 terms, even if we add the 4,000 cross references contained in the book to that sum. Interestingly, the list does not include the key two words from the title – "automation technics" – which is a fairly arcane term that nets fewer than 200 hits on Google and for which no entry can be found in the book itself.
Physically, the book is solid, has a nice heft, and is visually appealing. Inside, I found the display font to be readable and the layout to be fairly standard: guide words are displayed on the upper outboard side of each page (thus delineating terms for each pair of facing pages), with entries arranged in two columns beneath. Entries are arranged alphabetically in English, with German, French, and Russian equivalents listed below each entry. Entries occupy about 65% of the book's approximately 1000 pages; the rest of the volume is divided into indexes listing German, French, and Russian terms with corresponding numbers pointing to the entries in the main part of the book. I reviewed the book primarily as to its usefulness to a translator working in the Russian and English language pair, though I did make use of my French and German skills at times in my review.
Apropos of the theory of information, it is said that "information is proportional to astonishment," meaning that the value of information rises depending on how surprising it is. An example of high information content in terminology is the pairing of the term “eigenvector” with the term //собственный вектор//, because the pairing is surprising, i.e., one cannot easily derive one from the other without special knowledge (of, say, German or mathematics). An example of low information content—which I found to occur uncomfortably often during my review—might be the term “processing capability” (//возможность обработки//), which is followed by “processing capacity” (//производительность обработки//), “processing cycle” (//цикл обработки//), “processing method” (//метод обработки//), “processing module” (//модуль обработки//), and five more entries that follow the same basic scheme of modifier + noun, where no individual word is much of a mystery. (It might be argued that, in cases such as this, definitions given for the other languages might have higher information content, thus justifying their inclusion in a dictionary, but I did not find this to be the case: typically, all three definitions were simply combinations of otherwise ordinary words.)
In addition, I found the equivalent terms given for entries to be too brief, rarely exceeding two alternatives offered for a term. This tends to reduce the usefulness of the dictionary, in my opinion, since a number of terms end up short-shrifted. For example, only //чувтствительный элемент// and //детектор// are given in the entry for “sensor,” ignoring the widely used term //датчик// and the less popular //сенсор// (forms of which are nonetheless used in this dictionary for all Russian terms where sensor is used as a modifier). Similarly, “fluid flow control” is rendered as //регулирование потока жидкости//, leaving the quite serviceable (and in my mind, preferable) term //регулирование расхода жидкости// out in the cold. A byproduct of this brevity is a strong flavor of inconsistency as you encounter various other, correct ways of rendering words in other entries.
There is evidence of poor proofreading here and there in the book, things you would not expect to find so often in a high-end book from a serious publisher. Perhaps the most egregious example I found was the use of principle for principal in both an entry and a cross reference pointing to that entry.
What annoyed me more about this dictionary was the uncomfortably common occurrence of entries about which I have serious doubts. The entry that got me started in this direction was “process control system,” which is rendered unashamedly (and literally) as //технологическая контрольная система// (and although the immediately preceding entry – “process control simulation”|//моделирование управления процесса// – gets the "control" part right and improves on the "process" modifier, there is no hint anywhere of what I think is a fairly standard rendering: //система управления технологическим процессом//).
As another example, “process equipment design” is rendered as //проектирование оборудования//, which doesn't tell the whole story, i.e., the rendering back-translates simply as “equipment design.” Looking up //эталонное напряжение// gets you “primary voltage,” a term most readily associated with transformer inputs, instead of my preferred term, “reference voltage,” which has somewhat wider applicability. And blindly using terms such as “unit operation” for //основная операция//, “off-hook” for //разъединенный//, or “off-load” for //без нагрузки// will lead you to down the primrose path to incorrect translation, more often than not.
In my mind, perhaps what is not in the dictionary is less worrying than what is, though this is still an issue. Are you looking for help distinguishing among processes that are //техинческие//, //технологические//, //промышленные//, or //производственные//? Look elsewhere. The first does not appear, the second appears only indirectly, while the last two seem to be used fairly interchangeably and inconsistently among various terms involving processes. Among other terms that I jotted down before opening the book for the first time, I found no entries for terms such as “ladder logic,” “relay logic,” “piping & instrumentation diagram,” “process flow diagram” (though an entry for “process diagram” comes close), or “simplified process description” (or any process description, for that matter).
In the end, if it were merely a matter of what I perceive to be an excess of common word pairs among entries or the lack of some useful terms, then your buy/no-buy decision basically would boil down to answering the question: "How useful will this book be to me?" Indeed, such a tome might be very useful to someone just starting out in this area of technical translation. However, I feel the brevity of the entries and the occurrence of a number of entries with whose renderings I would take issue drastically reduces the book's usefulness to the less experienced translator. Thus, overall, I find it difficult to recommend this book.
//Alex Lane is certified by the ATA to translate from Russian into English. Before devoting himself full-time to translation and interpretation, Mr. Lane worked for nearly a decade as a licensed professional engineer (P.E., Florida, currently inactive) in the fields of control system design and implementation and computer engineering.//
{{{
[img[title|filename]]
[img[filename]]
[img[title|filename][link]]
[img[filename][link]]
}}}
Images can be included by their filename or full URL. It's good practice to include a title to be shown as a tooltip, and when the image isn't available. An image can also link to another tiddler or or a URL
[img[Romanesque broccoli|fractalveg.jpg][http://www.flickr.com/photos/jermy/10134618/]]
{{{
[img[Fractal vegetable|fractalveg.jpg]]
[img[This is shown as a tooltip|http://example.com/image.jpg]]
[img[http://example.com/image.jpg]]
[img[http://example.com/image.jpg][ExampleDotCom]]
}}}
The tooltip is optional.
[<img[Forest|forest.jpg][http://www.flickr.com/photos/jermy/8749660/]][>img[Field|field.jpg][http://www.flickr.com/photos/jermy/8749285/]]You can also float images to the left or right: the forest is left aligned with {{{[<img[}}}, and the field is right aligned with {{{[>img[}}}.
@@clear(left):clear(right):display(block):You can use CSS to clear the floats@@
{{{
[<img[A woody bit of Hampstead Heath|forest.jpg]]
[>img[A field near Milton Keynes|field.jpg]]
}}}
There's now an option under InterfaceOptions to allow TiddlyWiki's animation effects to be turned off.
#displayArea {background-color: #ffccff; }
#mainMenu {border: 1px solid #ffff88; }
#commandPanel {background-color: #008800; }
config.animFast = 0.12; // Speed for animations (lower == slower)
config.animSlow = 0.01; // Speed for EasterEgg animations
config.views.wikified.toolbarEdit.text = "Edit away, it won't get saved";
TiddlyWiki is being used for all kinds of things:
* EliseSpringer, a philospher at Wesleyan University in Connecticut, USA, is using TiddlyWiki for her homepage at http://espringer.web.wesleyan.edu/ and for [[ReasoningWell|http://reasoningwell.tiddlyspot.com/]], a wiki for her Philosophy faculty
* The website of a [[body-building club in Paris|http://www.superphysique.net/]]
* Teachers in Massachusetts to [[teach mathematics|http://luceatlux.net/mcasmath10/]]
* Schools in South Australia to [[distribute class materials to students|https://secure.ait.org/wiki/background.htm]]
* ChrisJohnson's [[personal home page|http://www.spkml.com/]]
* JacksonBoyle's collection of [[recipes|http://jacksonboyle.com/kitchen.htm]]
* JonathanCamp's guide to [[Prince 2 project management|http://www.microupdate.net/cms/doc/PrinceII.html]]
* BrandonSiegel's [[Case Personal Security Device Project|http://anubis.case.edu/398n]]
* MichaelDansie's site for the [[American Cryptogram Association|http://msig.med.utah.edu/RunningUtes/cryptogram/aca.html]]
* BrianHolland's [[student nodes|http://www.acsu.buffalo.edu/~bholland/]] from Buffalo Law School
* RuiCarmo's [[Python Grimoire|http://the.taoofmac.com/space/Python/Grimoire]], a sort of recipe book for the programming language Python
* Rich Kulesus' [[themer's blog|http://www.skinyourscreen.com/mrbiotech/]]
* Qliner Software are using TiddlyWiki to create the site for their [[hotkeys|http://www.qliner.com/hotkeys/]] product
* AndreasKänner's family home page at http://www.kaenner.de/
* MarkWygent of Wygent Reeds, a maker of Scottish bagpipe reeds from Delaware, has compiled a fascinating home page using TiddlyWiki at http://www.wygent.com/
* ChristopherJames has compiled a comprehensive guide to TabletPCs at http://www.tabletpcwiki.net/
* MiguelCentellas has created an extensive guide to Bolivian politics at http://www.centellas.org/politics/politiddly.html
* BrunoTiagoRodrigues has created a geocaching community site in Portuguese at http://travelbugrace.geocaching-pt.net/.
* CharlesStross, a celebrated British ScienceFiction writer, has used TiddlyWiki for his 'Tough Guide to the Rapture of the Nerds' at http://www.antipope.org/charlie/toughguide.html.
* KristofferNilausOlsen, a member of the Danish Student Group of Amnesty International, has used TiddlyWiki to collate reports of breaches of human rights. His site is at http://www.resultat.dk/sg/tw/students.html.
* MartinSilcock, an brand researcher working with Millward Brown, is using TiddlyWiki for his homepage at http://www.explorate.co.uk/.
* Many people are using the GTDTiddlyWiki variant for personal productivity, and there's been some interesting experiments in TiddlyWikiFiction.
Like most wikis, TiddlyWiki supports a range of simplified character formatting:
| !To get | !Type this |h
| ''Bold'' | {{{''Bold''}}} |
| --Strikethrough-- | {{{--Strikethrough--}}} |
| __Underline__ | {{{__Underline__}}} (that's two underline characters) |
| //Italic// | {{{//Italic//}}} |
| Superscript: 2^^3^^=8 | {{{2^^3^^=8}}} |
| Subscript: a~~ij~~ = -a~~ji~~ | {{{a~~ij~~ = -a~~ji~~}}} |
| @@highlight@@ | {{{@@highlight@@}}} |
<<<
The highlight can also accept CSS syntax to directly style the text:
@@color:green;green coloured@@
@@background-color:#ff0000;color:#ffffff;red coloured@@
@@text-shadow:black 3px 3px 8px;font-size:18pt;display:block;margin:1em 1em 1em 1em;border:1px solid black;Access any CSS style@@
<<<
//For backwards compatibility, the following highlight syntax is also accepted://
{{{
@@bgcolor(#ff0000):color(#ffffff):red coloured@@
}}}
@@bgcolor(#ff0000):color(#ffffff):red coloured@@
If you've any comments, corrections or observations about TiddlyWiki, the best way to get our attention is to write a blog entry, or post to the [[Community]] groups.
FireFox lets you SaveChanges in TiddlyWiki, but you will see up to three dialogs asking your permission for the local file operations. You must allow all three operations for it to work properly. Note that you can select the //Remember this decision// option to avoid seeing the dialogs in future.
<<<
You can run into problems if you accidentally click 'Deny' on the dialog, and select //Remember this decision//.
To reverse the effects, first locate the file {{{prefs.js}}} in your FireFox profile directory. Under Windows you'll find it at something like {{{C:\Documents and Settings\Jeremy\Application Data\Mozilla\Firefox\Profiles\o3dhupu6.default\prefs.js}}}, where {{{Jeremy}}} is the name of your windows profile and {{{o3dhupu6}}} will be a similar string of gobbledegook. On the Mac it'll be at {{{~/Library/Application Support/Firefox/Profiles/o3dhupu6.default/prefs.js}}} and on most versions of Linux, at {{{~/.mozilla/firefox/o3dhupu6.default/prefs.js}}}.
Open the file in a text editor and find the line {{{user_pref("capability.principal.codebase.p0.denied", "UniversalXPConnect");}}} and simply replace the word {{{denied}}} with {{{granted}}}.
//(Thanks to JonScully for figuring out this fix)//
<<<
FireFox users should be aware that GreaseMonkey can break TiddlyWiki. There's also a rather unpredictable FireFoxKeyboardIssue.
Under FireFox, TiddlyWiki can get into a state where it ignores the arrow keys on the keyboard but accepts ordinary alphanumeric input. The triggers for this behaviour are unclear, but it doesn't just affect TiddlyWiki. The solution appears to be to locate the file {{{compreg.dat}}} in your FireFox profile folder and rename it to {{{compreg.dat.old}}}.
Released in September 2004, the [[first version|firstversion.html]] was pretty basic, weighing in at 52KB.
The folks over at [[memorizable.org|http://memorizable.org]] have done some pretty interesting coding to come up with a ~JavaScript file that adds "flash card" functionality to tables.
Clicking on either ''English'' or ''Russian'' headers in the following tables does the following:
* Clears the table
* Randomizes the rows
* Displays one of the entries from the //other// column (the column whose header you didn't select) on the first blank line.
At this point, you should mentally guess what the corresponding entry should be. Once you have an idea (or give up), click on the 'show answer' button and indicate whether you guessed right or wrong. If you guessed correctly, another entry will appear on the next line, and so on. If you guessed wrong, the entry is cleared and another appears in its place.
An alternative way of using the feature is in matching mode, where you click matching pairs of table entries from the left and right columns.
This is a pretty neat resource for when you have to commit a number of terms to memory.
<html>
<br style="font-weight: bold;" />
<table width="90%" cellspacing="1" cellpadding="1" border="1" align="" summary="">
<caption style="font-weight: bold;">Example Flash Card Table</caption>
<tbody>
<tr>
<th width="50%"><a href="#" id="memorizeLink" onclick="return Mem.start( this )">English</a><br /> </th>
<th width="50%"><a href="#" id="memorizeLink" onclick="return Mem.start( this )">Russian</a><br /></th>
</tr>
<tr>
<td>list of abbreviations</td>
<td>список сокращений</td>
</tr>
<tr>
<td>scanning antenna</td>
<td>антенна кругового обзора</td>
</tr>
<tr>
<td style="vertical-align: top;">air duct fan</td>
<td style="vertical-align: top;">вентилятор воздуховода</td>
</tr>
</tbody>
</table>
</html>
Here's one way to get a Flickr badge in TiddlyWiki:
<html>
<a href="http://www.flickr.com" style="text-align:center;">www.<strong style="color:#3993ff">flick<span style="color:#ff1c92">r</span></strong>.com</a><br>
<iframe style="background-color:#ffffff; border-color:#ffffff; border:none;" width="113" height="151" frameborder="0" scrolling="no" src="http://www.flickr.com/apps/badge/badge_iframe.gne?zg_bg_color=ffffff&zg_person_id=zg_person_id=44218706%40N00&zg_set_id=289690&zg_context=in%2Fset-289690%2F" title="Flickr Badge"></iframe>
</html>
Here's the HTML code to insert in a tiddler:
{{{
<html>
<a href="http://www.flickr.com" style="text-align:center;">www.<strong style="color:#3993ff">flick<span style="color:#ff1c92">r</span></strong>.com</a><br>
<iframe style="background-color:#ffffff; border-color:#ffffff; border:none;" width="113" height="151" frameborder="0" scrolling="no" src="http://www.flickr.com/apps/badge/badge_iframe.gne?zg_bg_color=ffffff&zg_person_id=44218706%40N00&zg_set_id=289690&zg_context=in%2Fset-289690%2F" title="Flickr Badge"></iframe>
</html>
}}}
You'll need to know your Flickr person ID, which should replace the value "35468148136%40N01" in the HTML. There's a useful [[Flickr idGettr|http://eightface.com/code/idgettr/]] to help with this.
We at Galexi Wordsmiths don't rely on those lawyer-inspired paragraphs that folks like to append to outgoing emails, full of sound and fury and promising the wrath of Providence should the content of the message be used, copied, disclosed, etc. by anyone who is not "the intended recipient." Call us naive, but most people who might mistakenly receive such a message and anyone who goes to the trouble of actually //intercepting// a message as it passes through any of several machines on its way to its destination is not likely to be deterred by such threats.
Historically, the Internet has been a notoriously insecure medium for keeping secrets, especially in electronic mail, because most data is sent unencrypted from computer to computer, and intercepting packet traffic between computers is almost child's play. That's why, if you're serious about the security of the information you send out through your Internet connection, you should encrypt any sensitive information (and some experts recommend encrypting //all// of your communications, but I digress...).
One of the best tools for doing encryption and authentication that is a program called the GNU Privacy Guard, or GPG. There isn't space here to explain all the details of how it works, but there are many good references on the Internet. Basically, in order to send me a secure message using GPG, you'll need to get a copy of the program (it doesn't cost anything, as it's an open source application), you'll need to generate your own matched private and public keys, and you'll need my "public key," which is shown below.
{{{
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.1 (MingW32)
mQGiBEYdJDARBACXnfgI3uu4oqBND19SGoLAYyRWulePdccj6zL/0J6+/P5eazh8
/7YI+Yv1gzon6WPGisCKd6hvfoNReWCKStWESYJ347jCUxmITHwtWQS6PBaQzPsh
JcXrhMap8q5Q7zT5skXgXt1VObuVv5ViDrZvHDXbTnZmnjW5W9BH9hKd+wCgkwwA
7e63yibFQhAjIj/ZSZf6dXUD/3z+EQXZ/HLCC+vBPDbRuD1MRnI3aS5L/b3LP66r
9BYminSmns9hd9BoJIIGfgdoPRT+TLFSoPnw4woXFpELYJ3tziRNT0NbF8n1zlqs
EI6rJ7OGSPPCPy8Ijm+lFTaetBUCGMG9mKBVx3oMG8mgdnUcKd7uWilcit6avpiY
qUydA/9XFmmgP4/f0w+Z7qO8uauX+WhfESJasaFpb+0FlgHqrOI6o10zL086uZ/a
K/JissjU7a2MB2EpPJlyvikd9Xn9ewIM1bwJxzW2BtcJ92HrzCKCdp03JG3YNl6u
UnluZxSEpJuGjF/A0mHHG9PruIfXaKljtntBQIe4VW1c7gmtyrQ1QWxleCBMYW5l
IChHYWxleGkgV29yZHNtaXRocywgTExDKSA8d29yZHNAZ2FsZXhpLmNvbT6IWQQT
EQIAGQUCRh0kMAQLBwMCAxUCAwMWAgECHgECF4AACgkQ5jHN2lBlmGYY6wCePEHv
/Rj7qh693TqNpd0PC/OgAp4AoJDhHWCG2NofiOqlcSQPImJmZliiuQINBEYdJDsQ
CADG2SjQa1w6o5q9zW2bHFBCTbEs9k3Wxcj05oKDKHTLqs5uSnw10pt8VfM+B/K8
oi+w3LDcFZ0Z9wG8ac4kdeOH+1Ow4u8XcNKTwQYJb5ZO2nZSSYFAXpJyt4/rdX9+
YdrSA+kvoLTbHqnzYzURyUkoBBmWpvm8+5p3FSlJmJoq0ffXBAl4V1UtTumdWQ7i
W7XJ/A+rcg3qn1YmL4uoB3gPBwmr1NKatwUSr9W6bnPe7mqKlbBEwf709L1takfC
fnIA737pGV5JHBwR6xwdh5gWMEG2PllYw8sffKlaHEENXm+snHvYFOpIPxjZ83dG
s0CkjDOlB1/8pwngfOrWtYXrAAMGB/91BTGYuwA8xqfkb6NKpSNcXO3x+y+KL9QA
JBYpGCCCuYPFVHtROztlI0IQ/4/Q8IHgAZyAJdAi5v76mIWVGCOwVdcTQ3oejkHJ
K9JG5TLjUeT1JJl0GbSvRkr0B1KtWHpnTV19C2CSUH3L0Rrf2HWStF5L6pghm8wY
XqI12sNyFGrLt2DwAr6GLg1xQbaAbf2HqG3pimI0izs9EuGojcpsONbXwocpaM72
durVOXAjv8n0UYHWbHX2eQkJlhIhMvjgLjgSd6uzybbV9ev6BX3TvVHJviyF4DNw
iRmKWwwMJRTCeKipBYowVPIZRThU9ASGvBzGNYk8fo9z0dMT1b23iEYEGBECAAYF
AkYdJDsACgkQ5jHN2lBlmGa7MQCbBCBpdmMKrXuIog4ygioWmhEb+u0AoIQ2drcr
DPSgx74DZhD/16RhVp1K
=63HR
-----END PGP PUBLIC KEY BLOCK-----
}}}
The easiest way to save this key (assuming you are using a Windows Web browser such as Firefox or Internet Explorer) is to:
* click inside the scrolling field with your mouse and type ~Ctrl-A, to highlight the contents of the field.
* type ~Ctrl-C to copy the highlighted text to the Windows Clipboard.
* open Windows Notepad (or your favorite text editor) and type ~Ctrl-V, to paste the text in the editor.
* save the file.
See the GPG instructions to learn how to import the key into your keyring, and on how to use it for encrypting information. While you're doing that, read up on how to export your own public key, which you can then send to me (or anyone else) to be used when sending messages to you.
Clients and potential clients who send unencrypted information via email will be assumed to be content with the level of security such transmission affords, and unless otherwise requested, unencrypted responses will be sent to such email recipients.
NathanBower's GTDTiddlyWiki is a popular adaptation of TiddlyWiki geared towards DavidAllen's GettingThingsDone methodology for personal productivity. The [[original|http://shared.snapgrid.com/gtd_tiddlywiki.html]] is based on an obsolete, older version of TiddlyWiki; if you want to have the GTD look-and-feel but still be able to use the latest TiddlyWiki features, check out the GTD Style at [[TiddlerWiki|http://tiddlystyles.com/#GTDStyleSheet]]
A new feature for the ThirdVersion of TiddlyWiki is the ability to generate an RssFeed of its content. You can flick it on with a new addition to the InterfaceOptions. If enabled, it automatically saves an RSS 2.0 format file with the last few changed tiddlers in it. It's given the same filename as the TiddlyWiki file but with the ".xml" extension. Like all TiddlyWiki features, it's experimental, and will probably be a bit temperamental in your feedreader until the bugs are ironed out.
Note that you must set the tiddler SiteUrl to be the URL where your TiddlyWiki will be published. (Don't put leading spaces or line breaks before or after the URL).
The easiest way to learn about TiddlyWiki is to use it! Try clicking on various links and see what happens - you cannot damage tiddlywiki.com or your browser. (Use the <<closeAll>> button over on the right to clear all the displayed tiddlers and start again).
There is an extensive [[Community]] [[documentation wiki|http://www.tiddlywikiguides.org/]], including an invaluable [[FAQ|http://tiddlywikiguides.org/index.php?title=TiddlyWiki_FAQ]]. Other useful guides include:
* Dave Gifford's [[TiddlyWiki for the Rest of Us|http://www.giffmex.org/twfortherestofus.html]]
* Morris Gray's [[TW Help - TiddlyWiki help file for beginners|http://tiddlyspot.com/twhelp/]]
* DmitriPopov's [[TiddlyWiki quick reference card|http://nothickmanuals.info/doku.php/cheatsheets]].
When you're ready to create your own TiddlyWiki on your computer, follow the instructions in DownloadSoftware and SaveChanges. There is also a free hosted service at http://tiddlyspot.com/ that makes it easier to share your TiddlyWiki with others (for more demanding applications there are several other ServerSide solutions available). There are also a couple of introductory screencasts from [[JimVentola|http://faculty.massasoit.mass.edu/jventola/videocasts/tidhelp2/tidhelp2.html]] and [[LeonKilat|http://max.limpag.com/2006/09/07/using-a-tiddlywiki-a-video-guide/]].
|''URL:''|http://gimcrackd.com/etc/src/|
|''Description:''|Gimcrack'd: Code and Other Oddments|
|''Author:''|ChrisKlimas|
<<gradient horiz #bbbbbb #eeeeee #ffffff>>The new GradientMacro allows simple horizontal and vertical coloured gradients. They are constructed from coloured HTML elements, and don't require any images to work.>>
The GradientMacro is an ExtendedMacro that processes the text after it up until the next '>>' sequence. It looks like this:
{{{
<<gradient vert #ffffff #ffdddd #ff8888>>gradient fill>>
}}}
The first parameter can be ''vert'' or ''horiz'' to indicate the direction of the gradient. The following parameters are two or more colours (CSS RGB(r,g,b) format is also acceptable). The GradientMacro constructs a smooth linear gradient between each of the colours in turn.
| <<gradient vert #ffffff #ffdddd #ff8888>>No images were harmed in the making of this gradient fill>> | <<gradient vert #ffffff #ddffdd #88ff88>>No images were harmed in the making of this gradient fill>> | <<gradient vert #ffffff #ddddff #8888ff>>No images were harmed in the making of this gradient fill>> |
Inline CSS definitions can be added to gradient filles like this:
<<gradient vert #000000 #660000 #aa2222>>color:#ffffff;font-size:12pt;Darkness>>
{{{
<<gradient vert #000000 #660000 #aa2222>>color:#ffffff;font-size:12pt;Darkness>>
}}}
Several popular GreaseMonkey scripts can cause some or all features of TiddlyWiki to stop working - the default Linkify script seems to be particularly troublesome. There doesn't seem to be a //solid// way to disable GreaseMonkey from within TiddlyWiki (which is technically entirely understandable but does lead to a fairly grim user experience).
/***
|Name|HelloWorldMacro|
|Created by|SimonBaird|
|Location|http://simonbaird.com/mptw/#HelloWorldMacro|
|Version|1.1|
|Requires|~TW2.x|
!Description
It's a Hello World TiddlyWiki macros.
!History
* 11-Jan-06, version 1.1, updated for ~TW2.0
!Examples
|!Source|!Output|h
|{{{<<helloWorld dude>>}}}|<<helloWorld dude>>|
|{{{<<helloWorld 'to everyone'>>}}}|<<helloWorld 'to everyone'>>|
(You can use (single or double) quotes or double square brackets for params with spaces)
!Notes
This is intended to help you get started with customising your TW. To make the macro work you have to give this tiddler a tag of systemConfig then save and reload. To learn more about customising Tiddlywiki? Look at other people's plugins or... click View, Source in your browser and start reading. :)
!Code
***/
//{{{
config.macros.helloWorld = {};
config.macros.helloWorld.handler = function (place,macroName,params,wikifier,paramString,tiddler) {
var who = params.length > 0 ? params[0] : "world";
wikify("Hello //" + who + "// from the '" + macroName + "' macro in tiddler [[" + tiddler.title + "]].", place);
}
//}}}
This is an advanced option that lets you choose whether editting features are shown when a TiddlyWiki file is viewed over {{{http:}}} (as opposed to {{{file:}}}).
To publish a TiddlyWiki with the editting features hidden you'll need to create a tiddler tagged with 'systemConfig' and include in it the line:
{{{
config.options.chkHttpReadOnly = true;
}}}
End users can then override the setting using the AdvancedOptions panel.
/***
| Name|HideWhenPlugin|
| Description|Allows conditional inclusion/exclusion in templates|
| Version|3.0 ($Rev: 1845 $)|
| Date|$Date: 2007-03-16 15:19:22 +1000 (Fri, 16 Mar 2007) $|
| Source|http://mptw.tiddlyspot.com/#HideWhenPlugin|
| Author|Simon Baird <simon.baird@gmail.com>|
| License|http://mptw.tiddlyspot.com/#TheBSDLicense|
For use in ViewTemplate and EditTemplate. Example usage:
{{{<div macro="showWhenTagged Task">[[TaskToolbar]]</div>}}}
{{{<div macro="showWhen tiddler.modifier == 'BartSimpson'"><img src="bart.gif"/></div>}}}
***/
//{{{
window.removeElementWhen = function(test,place) {
if (test) {
removeChildren(place);
place.parentNode.removeChild(place);
}
};
merge(config.macros,{
hideWhen: { handler: function(place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( eval(paramString), place);
}},
showWhen: { handler: function(place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( !eval(paramString), place);
}},
hideWhenTagged: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( tiddler.tags.containsAll(params), place);
}},
showWhenTagged: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( !tiddler.tags.containsAll(params), place);
}},
hideWhenTaggedAny: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( tiddler.tags.containsAny(params), place);
}},
showWhenTaggedAny: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( !tiddler.tags.containsAny(params), place);
}},
hideWhenTaggedAll: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( tiddler.tags.containsAll(params), place);
}},
showWhenTaggedAll: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( !tiddler.tags.containsAll(params), place);
}},
hideWhenExists: { handler: function(place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( store.tiddlerExists(params[0]) || store.isShadowTiddler(params[0]), place);
}},
showWhenExists: { handler: function(place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( !(store.tiddlerExists(params[0]) || store.isShadowTiddler(params[0])), place);
}}
});
//}}}
You can divide a tiddler into
----
sections by typing four dashes on a line by themselves
The core TiddlyWiki code is regularly updated with bug fixes and new features. If you're using an earlier revision of TiddlyWiki, here's the simple way to upgrade to the latest version:
* Open your TiddlyWiki file in FireFox (say it's called "mystuff.html")
* SaveChanges (with SaveBackups switched on) to make sure that you've got a backup of it
* Without closing that page, right-click on [[this link|http://www.tiddlywiki.com/empty.html]], select 'Save target' or 'Save link' and save it as "mystuff.html", replacing your existing file
* Now go back to the previously opened copy of "mystuff.html" in your browser and SaveChanges again. It will inherit the newly saved code
* Refresh the page in the browser to verify that the upgrade has worked
The most likely cause of the upgrade process not working properly is that one of the [[Plugins]] you're using is not compatible with a change in the new release. If so, you can use the [[ImportTiddlersPlugin|http://www.tiddlytools.com/#ImportTiddlersPlugin]] from TiddlyTools to selectively import your content and [[Plugins]] into a new empty TiddlyWiki.
Entities in HTML documents allow characters to be entered that can't easily be typed on an ordinary keyboard. They take the form of an ampersand (&), an identifying string, and a terminating semi-colon (;). There's a complete reference [[here|http://www.htmlhelp.com/reference/html40/entities/]]; some of the more common and useful ones are shown below. Also see [[Paul's Notepad|http://thepettersons.org/PaulsNotepad.html#GreekHtmlEntities%20HtmlEntitiesList%20LatinHtmlEntities%20MathHtmlEntities]] for a more complete list.
|>|>|>|>|>|>| !HTML Entities |
| &nbsp; | | no-break space | | &apos; | ' | single quote, apostrophe |
| &ndash; | – | en dash |~| &quot; | " | quotation mark |
| &mdash; | — | em dash |~| &prime; | ′ | prime; minutes; feet |
| &hellip; | … | horizontal ellipsis |~| &Prime; | ″ | double prime; seconds; inches |
| &copy; | © | Copyright symbol |~| &lsquo; | ‘ | left single quote |
| &reg; | ® | Registered symbol |~| &rsquo; | ’ | right single quote |
| &trade; | ™ | Trademark symbol |~| &ldquo; | “ | left double quote |
| &dagger; | † | dagger |~| &rdquo; | ” | right double quote |
| &Dagger; | ‡ | double dagger |~| &laquo; | « | left angle quote |
| &para; | ¶ | paragraph sign |~| &raquo; | » | right angle quote |
| &sect; | § | section sign |~| &times; | × | multiplication symbol |
| &uarr; | ↑ | up arrow |~| &darr; | ↓ | down arrow |
| &larr; | ← | left arrow |~| &rarr; | → | right arrow |
| &lArr; | ⇐ | double left arrow |~| &rArr; | ⇒ | double right arrow |
| &harr; | ↔ | left right arrow |~| &hArr; | ⇔ | double left right arrow |
The table below shows how accented characters can be built up by subsituting a base character into the various accent entities in place of the underscore ('_'):
|>|>|>|>|>|>|>|>|>|>|>|>|>|>|>|>|>| !Accented Characters |
| grave accent | &_grave; | À | à | È | è | Ì | ì | Ò | ò | Ù | ù | | | | | | |
| acute accent | &_acute; | Á | á | É | é | Í | í | Ó | ó | Ú | ú | | | Ý | ý | | |
| circumflex accent | &_circ; | Â | â | Ê | ê | Î | î | Ô | ô | Û | û | | | | | | |
| umlaut mark | &_uml; | Ä | ä | Ë | ë | Ï | ï | Ö | ö | Ü | ü | | | Ÿ | ÿ | | |
| tilde | &_tilde; | Ã | ã | | | | | Õ | õ | | | Ñ | ñ | | | | |
| ring | &_ring; | Å | å | | | | | | | | | | | | | |
| slash | &_slash; | | | | | | | Ø | ø | | | | | | | |
| cedilla | &_cedil; | | | | | | | | | | | | | | | Ç | ç |
//Note that the popular [[Firebug|http://www.joehewitt.com/software/firebug/]] extension for Firefox interferes with ImportTiddlers if its "Show XMLHttpRequest" option is switched on//
<<importTiddlers>>
<html>
<br style="font-weight: bold;" />
<table width="80%" cellspacing="1" cellpadding="1" border="1" align="" summary="">
<caption style="font-weight: bold;">Caught While Editing...</caption>
<tbody>
<tr>
<th>Russian Original</th>
<th>Unedited English Translation</th>
<th>Edited Translation</th>
<th>Comment</th>
</tr>
<tr>
<td>провести испытания шланга XYZ...</td>
<td>conduct tests of hose XYZ...</td>
<td>test hose XYZ...</td>
<td></td>
</tr>
<tr>
<td>провести внешний осмотр...</td>
<td>conduct a visual inspection of...</td>
<td>visually inspect...</td>
<td></td>
</tr>
</tbody>
</table>
</html>
When you type more than three characters in the search box at the upper right, any matching tiddlers are automatically displayed with the text highlighted. There's a couple of minor issues: the highlights don't get removed when you clear the search, and occasionally, on some browsers, keystrokes get missed if you type quickly so you may need to click the 'search' button to manually trigger the search.
TiddlyWiki lets you write ordinary HTML by enclosing it in {{{<html>}}} and {{{</html>}}}:
<html>
<a href="javascript:;" onclick="onClickTiddlerLink(event);" tiddlyLink="TiddlyWiki" style="background-color: yellow;">Link to wikiwords from HTML</a>
</html>
The source for the above is:
{{{
<html>
<div style="background-color: yellow;">
<a href="javascript:;" onclick="onClickTiddlerLink(event);" tiddlyLink="Macros">Link to wikiwords from HTML</a>
</div>
</html>
}}}
HTML can enable some exotic new features (like [[embedding GMail and Outlook|http://groups.google.com/group/TiddlyWiki/browse_thread/thread/d363303aff5868d0/056269d8409d121f?lnk=st&q=embedding+gmail&rnum=1#056269d8409d121f]] in a TiddlyWiki). However it doesn't work for some JavaScript code libraries; see CustomMarkup for another way to include custom HTML in your TiddlyWiki.
[[Plugins]] are just tiddlers containing JavaScript code that is tagged with <<tag systemConfig>>. TiddlyWiki executes any [[Plugins]] as it loads; they can add [[Macros]] or otherwise extend and enhance the base code.
The recommended way to install a plugin into your own copy of TiddlyWiki is to use ImportTiddlers (there are instructions for ManuallyInstallIngPlugins when required).
InterfaceOptions are displayed when you click the 'options' button on the right. They are saved in a cookie on your browser, making them sticky between visits:
<<<
<<tiddler OptionsPanel>>
<<<
* The user name for edits should be set //before// starting to edit things (ouch. another bug)
* SaveBackups gives the option of whether to generate backup files
* AutoSave gives the option of automatically saving every time a change is made
* RegExpSearch allows more complex search expressions
* CaseSensitiveSearch does as its name implies
TiddlyWiki works on InternetExplorer 6.x and above under Windows. It also allows you to SaveChanges, albeit there are some annoying XP ServicePack2Problems and VistaIssues to work around.
Known problems with TiddlyWiki under InternetExplorer:
* [[Gradient]] fills sometimes appear in the wrong place until you move the mouse over the tiddler
* Horizontal gradients don't work correctly
* Links to tiddlers with multiple consecutive spaces in their titles is broken
* Runs of spaces within tiddlers get conflated into a single space when you edit a tiddler. This is particularly annoying when using MonospacedText blocks
|''URL:''|http://jackparke.googlepages.com/jtw.html|
|''Description:''|Plugins, Macros and Hacks|
|''Author:''|JackParker|
Offers a popup menu to jump directly to any of the currently open tiddlers. It is used with the ToolbarMacro like this:
{{{
<<toolbar jump>>
}}}
Access keys are shortcuts to common functions accessed by typing a letter with either the 'alt' (PC) or 'control' (Mac) key:
|!PC|!Mac|!Function|
|Alt-F|Ctrl-F|Search|
|Alt-J|Ctrl-J|NewJournal|
|Alt-N|Ctrl-N|NewTiddler|
|Alt-S|Ctrl-S|SaveChanges|
These access keys are provided by the associated internal [[Macros]] for the functions above. The macro needs to be used in an open tiddler (or the MainMenu or SideBar) in order for the access keys to work.
While editing a tiddler:
* ~Control-Enter or ~Control-Return accepts your changes and switches out of editing mode (use ~Shift-Control-Enter or ~Shift-Control-Return to stop the date and time being updated for MinorChanges)
* Escape abandons your changes and reverts the tiddler to its previous state
In the search box:
* Escape clears the search term
/***
|''Name:''|LegacyStrikeThroughPlugin|
|''Description:''|Support for legacy (pre 2.1) strike through formatting|
|''Version:''|1.0.2|
|''Date:''|Jul 21, 2006|
|''Source:''|http://www.tiddlywiki.com/#LegacyStrikeThroughPlugin|
|''Author:''|MartinBudden (mjbudden (at) gmail (dot) com)|
|''License:''|[[BSD open source license]]|
|''CoreVersion:''|2.1.0|
***/
//{{{
// Ensure that the LegacyStrikeThrough Plugin is only installed once.
if(!version.extensions.LegacyStrikeThroughPlugin) {
version.extensions.LegacyStrikeThroughPlugin = {installed:true};
config.formatters.push(
{
name: "legacyStrikeByChar",
match: "==",
termRegExp: /(==)/mg,
element: "strike",
handler: config.formatterHelpers.createElementAndWikify
});
} //# end of "install only once"
//}}}
|''URL:''|http://tw.lewcid.org/|
|''Description:''|a repository of my extensions for TW|
|''Author:''|SaqImtiaz|
The format for PrettyLinks allows for links that open local or network folders. Depending on your browser and operating system, the folders are opened in Windows Explorer, the OS X Finder, or the browser itself.
Edit this tiddler to see [[this link to a Windows network share|file://///server/share/folder/path/name]], [[this link to a Windows drive-mapped folder|file:///c:/folder/path/name]] and [[this link to a Unix-style folder|file:///folder/path/name]].
[[Macros]] let you write tiddlers containing more exotic objects than just text. Built-in macros include:
* NewJournalMacro and NewTiddlerMacro
* GradientMacro
* [[Sparklines]]
* TabMacro
* TaggingMacro
* TodayMacro
* ToolbarMacro
Tag popup:
{{{
<<tag features>>
}}}
will result in <<tag features>>
Slider:
{{{
<<slider chkTestSlider OptionsPanel options "Change TiddlyWiki advanced options">>
}}}
Results in this button <<slider chkTestSlider OptionsPanel options "Change TiddlyWiki advanced options">>
The parameters are:
* cookie name to be used to save the state of the slider
* name of the tiddler to include in the slider
* title text of the slider
* tooltip text of the slider
Out of the box, TiddlyWiki offers:
* Browsable with the vast majority of modern desktop browsers on Windows, Macintosh and Linux
* Ability to SaveChanges on:
** FireFox and Opera under all operating systems
** InternetExplorer under Windows
** [[Safari]] and [[Camino]] under OS X
** Minimo on Nokia 770
* Rich formatting including MonospacedText, ExtendedFormatting, NonWikiWordLinks, WikiWordEscape, PrettyLinks, SubHeadings, BulletPoints, NumberedBulletPoints, [[Tables]], BlockQuotes, HorizontalRules and the ability to use a CustomCssClass.
* Various InterfaceOptions, including the ability to GenerateAnRssFeed, SaveBackups and AutoSave
* KeyboardShortcuts so you can finish editing a tiddler with Control-Enter or abandon it with Escape
* InlineHTML
* [img[brixhamharbour.jpg][EmbeddedImages]]...EmbeddedImages:
* [[Macros]] providing rich interactive features, including [[Sparklines]] and [[Gradients|GradientMacro]]
* a flexible OpenSourceLicense
* a liquid CSS layout that can be customised with a CustomStyleSheet
* Extensive StartupParameters to control the behaviour of TiddlyWiki through specially crafted URLs
* There are [[translations]] of TiddlyWiki available in many languages, including [[Chinese]], [[French]], [[German]], [[Spanish]], [[Portuguese]]
The [[Community]] around TiddlyWiki has extended this basic functionality with a wide range of [[Plugins]] and TiddlyWikiAdaptations.
<html><center>
<a href="http://www.flickr.com" style="text-align:center;">www.<strong style="color:#3993ff">flick<span style="color:#ff1c92">r</span></strong>.com</a><br>
<iframe style="background-color:#ffffff; border-color:#ffffff; border:none;" width="113" height="151" frameborder="0" scrolling="no" src="http://www.flickr.com/apps/badge/badge_iframe.gne?zg_bg_color=ffffff&zg_person_id=44218706%40N00&zg_set_id=72157601128304652&zg_context=in%2Fset-72157601128304652%2F" title="Flickr Badge"></iframe>
</center></html>
[[Welcome, Visitor!]]
[[About Our Company]]
[[Contact Information]]
[[Site News]]
[[Testimonials]]
[[Sample Translations]]
[[Public Key|GNU Privacy Guard Public Key]]
----
^^Content © 2006-2007, Galexi Wordsmiths, LLC^^
----
^^[img[favicon.ico]] TiddlyWiki <<version>>
Software © 2007 [[UnaMesa|http://www.unamesa.org/]]^^
In some situations it can be useful to use the clipboard insead of InstallingPlugins using ImportTiddlers.
# Open a new browser window and navigate to the TiddlyWiki site containing the macro you want
# Double click the tiddler, or click the {{{source}}} button (on other sites it will sometimes be a {{{view}}} or {{{edit}}} button)
# The entire text of the tiddler should be selected; if not select it manually with Control-A or Command-A
# Copy the entire text of the tiddler to the clipboard
# Open your TiddlyWiki file in a new browser window
# Click {{{new tiddler}}} to create a new blank tiddler
## Paste the contents of the clipboard into it's body
## Set the title as appropriate
## Add the tag {{{systemConfig}}}
# Click {{{done}}} on the tiddler
# SaveChanges
# Reload your TiddlyWiki in the browser
The plugin should now be available for use.
|''URL:''|http://www.martinswiki.com/ |
|''Description:''|Martin Buddens's Plugins |
|''Author:''|MartinBudden |
MicroContent being a fashionable word for self-contained fragments of content that are typically smaller than entire pages. Often MicroContent is presented via some kind of aggregation that reduces the perceptual shock and resource cost of context switching (eg Blogs aggregating several entries onto a page or Flickr presenting photos in an album). This TiddlyWiki aggregates MicroContent items that I call 'tiddlers' into pages that are loaded in one gulp and progressively displayed as the user clicks hypertext links to read them.
Sometimes it's useful to stop a minor change to a tiddler from causing it to rise to the top of the timeline. This can be done by pressing the Shift key while clicking the 'done' toolbar button, or with the ~Shift-Control-Enter key. This behaviour can be switched to become the default with one of the AdvancedOptions.
The 'Missing' option on the MoreTab shows you the names of tiddlers that you've referred to but not gone ahead to define. It can be useful during writing sessions to keep track of things you need to come back and fill out.
|''URL:''|http://mptw.tiddlyspot.com/|
|''Description:''|a tiddlywiki distribution and plugins|
|''Author:''|SimonBaird|
{{{Monospaced text}}} is supported - edit this tiddler to see the syntax.
You can also have monospaced blocks (useful for source code):
{{{
var posTop = findPosY(e);
var posBot = posTop + e.offsetHeight;
var winTop = findScrollY();
var winHeight = findWindowHeight();
var winBot = winTop + winHeight;
if(posTop < winTop)
return(posTop);
else if(posBot > winBot)
{
if(e.offsetHeight < winHeight)
return(posTop - (winHeight - e.offsetHeight));
else
return(posTop);
}
else
return(winTop);
}}}
The functions of 'Timeline' and 'All' tabs have been around since the FirstVersion of TiddlyWiki. The purpose of the 'More' tab is to bring together some other, more specialised lists of tiddlers that can be useful during writing sessions. Currently, it offers lists of OrphanTiddlers and MissingTiddlers.
/***
| Name|MptwLayoutPlugin|
| Description|A package containing templates and css for the MonkeyPirateTiddlyWiki layout|
| Version|3.0 ($Rev: 1845 $)|
| Source|http://mptw.tiddlyspot.com/#MptwLayoutPlugin|
| Author|Simon Baird <simon.baird@gmail.com>|
| License|http://mptw.tiddlyspot.com/#TheBSDLicense|
!Notes
Presumes you have TagglyTaggingPlugin installed. To enable this you should have a PageTemp