Lingo Download
Raingarda Krzynowek
These points all have one thing in common in that we need to try and move away from the acronyms, verbiage, and lingo that was coined in a non-customer-centric world and based on optimization rather than value.
By default, Lingo will mark up any page with the terms and definitions defined on the Terminology page of your wiki (or the respective page in the language of your wiki).Create that page and insert some entries using the following syntax:
To structure the Terminology page, you are also allowed to have Terms and Definitions on separate lines.Any lines not starting with a semicolon (;) or a colon (:) are ignored, so go ahead and insert empty lines, headlines, explanatory text.
Using this format, you may assign one definition to multiple terms, e.g., to cover grammatical variants (see the U.S.A. example below), and multiple definitions to one term, e.g., to cover different meanings (see the ACK example). You may even combine this, i.e., have multiple definitions for a set of multiple terms. Finally, you may also use transclusion, e.g., to have different glossaries for different topics and pull them all together on the Terminology page.
The extension is pretty well internationalized by now, thanks to the efforts of the volunteers on (If your language is not supported yet, get an account there and help yourself. It's easy!) To find out the name of the Terminology page and of the __NOGLOSSARY__ magic word in your wiki's language, have a look at the files in the i18n folder and the Lingo.i18n.magic.php file. If you want to change the name of the Terminology page, you can do so by editing the page on your wiki named MediaWiki:lingo-terminologypagename.
MobileFrontend suppresses Lingo's styling, which makes all Definitions used on the article appear at the end of the page. To avoid this add the following to your LocalSettings.php when using MobileFrontend:
The Linguistics Organization at Florida State University (LINGO) is a collaborative, student-centered club founded on the premise of creating a community for all aspiring linguists at Florida State. Meetings consist of social gatherings as well as lectures from the faculty of the Department of Modern Languages and Linguistics to educate members not only on linguistics in general but also on the research interests of our department. Collaboration between undergraduate students, graduate students, and faculty is encouraged. The club hopes to expand awareness of the relevance of linguistics to the campus at large, as well as to promote the academic benefits of pursuing education in the field of linguistics. Students interested in joining LINGO can access our NoleCentral or follow us on Instagram @lingofsu for updates and information.
If you say "I need help with a feature in Creo", you are not telling me what app you are having issues with. It's natural for users to call "Creo Parametric" just Creo because we never had a platform that our apps where built on. So most of my users assume that Pro/E is now Creo and this is not the case. It's Creo Parametric.
So when you say "I need help with Creo" it's the same thing as saying I need help with Microsoft Office. Does not tell me much. If you say "I need help with Creo Parametric" it's the same as saying I need help my Excel.
The Microsoft analogy helped some of my users understand. I use the iPhone analogy for me tech. savy users and tell them that Creo is the iPhone and Creo Parametric is the app that runs on the iPhone for 3D Design.
People can choose to say what they like. In an environment were many Creo apps are being used, it's just not as clear when you refer to a particular app by the name of the platform. Most of my users are now aware of this because I simply took the time to explain it and it's not a big deal. It will still take time to stop saying Pro/E but if they need to break that habit, I might as well teach them the proper name to switch too.
If you want your users to call Creo Parametric just Creo, then it's perfectly fine. It get's a little confusing when you have multiple Creo apps and a mixture of how people refer to them. To keep things consistent and simple, I simply explained it to my users and we are all saying the same things.
I was just trying to get a feel for how many Administrators have taken the time to explain the new lingo. Once you do, it's much easier for them to understand it and in turn use the correct names for the apps they are using.
I've had an ordeal with an employee that started when he was hired. The question posed by the manager was something like "Do you have experience with Creo". The response was something like "...X number of years on Creo". (No, this manager did not consult me and there were no reviews of this users's capabilities".
I personally feel that PTC cause much of this confusion. If they would have allowed Pro/ENGINEER to retire gracefully and not change the name of Wildfire 5 mid way through it's life by calling it Creo Elements/Pro, there would be less confusion today.
If PTC would have left the Pro/E name alone, it would be much easier today for people to use the correct naming of the apps. The only thing we would need to really explain is the difference between Co/Create and Creo Direct. Creo Direct will eventually replace Co/Create but it currently only has limited functionality in comparison.
03c5feb9e7