Traveller talk:Projects

Sources

My next self appointed task is to return to the update of sources to use {{Ludography cite}}. I will also be fixing some named references now that I have a better understanding of the citation templates. —¿philoserf? (talk) 15:44, 23 June 2020 (EDT)

Dictionary

To do

• Vilani
• Trokh (Aslan)
• K'kree
• Gvegh (Vargr)
• Zdetl (Zhodani
• Oynprith (Droyne)

Nearly for the moment. I think I have gotten all articles categorized as dictionary entries in main space. Last current task is category:Aslan dictionary to category:Trokh dictionary.

I’ll take these on as new tasks one day:

• extract more dictionary entries from the original source materials
• find articles that are dictionary entries but are not categorized or organized as such
• update K’kree dictionary to !kree dictionary
• standardize/normalize dictionary entries including a potential {{word}} template

—¿philoserf? (talk) 14:49, 23 June 2020 (EDT)

Reference: Template:Languages Referral Tree and Languages of Charted Space

Based upon the list of languages from the sophont pages, here is the list of 65 named known languages:

A'Prur, Aaca, Aekhu (language), Anglic, Anseri, Asath, Clotho, Common Iltharan, Delphinic Trinary, Denaari, Detran, Droashav, Esar, Ginshari, Great Ape Language, Gurvin (language), Gvegh (language), Halkanese, Hhraki, Hsien, Irilitok (language), Iryakhtip, Jotal, K'kree Language, Kadli, Kafoe, Kehuu, Kha'thak, Klatha'sh, Liberti, Maganglic, Mal'Gnar (language), Mariel, Maskaan, Mavuri, Meroqua, Murrissi (language), N'Toz, Na, Neo-Chinese, Old Kurae, Ossiyaisaand, Ovaghoun (language), Oynprith, Raxkiir, Resimwo, Sagamaal, Savezitoiah, Sopas, Sylean Language, Takhil, Te-Zlodh, Telepathic, Tirrillese, Tobaian, Tring (language), Trokh, Vilani (language), Virsashi, Vrynsyss, Wawa-pakekeke-wawa, Yerkish, Yiirabarhi, Yslai, Z'krall, Zdetl

- Tjoneslo (talk) 22:22, 22 June 2020 (EDT)

Conversation

I think this will be my next task. I’ll be in and out, off and on, for a few weeks and sought a task I could do in bursts.

Project Traveller:Projects#Dictionary mentions categories and and style. I am aware of Manual of Style#Dictionary Article Entries, the “good example” of dictionary:Fiwai'al and Fiwai'al, the {{DE}}, and the {{DEN}}.

Q1) Are there any categories to think about other than X dictionary?
Q2) Any known gotcha that didn’t make the docs?

I’ve made a few mistakes by using an example already in the Dictionary namespace as an example. This leads me wrong. I will fix those changes first.

—¿philoserf? (talk) 00:27, 21 June 2020 (EDT)

I have not thought of any additional categories that would be useful if you think of any please feel free to add them. One request, please leave the level 2 heading with the language name (e.g. == Vilani ==), as a plain word (no links). Tjoneslo (talk) 05:57, 21 June 2020 (EDT)

The level 2 language was one of the first mistakes I recognized once I found that entry in the style guide. Will do. I’ll be putting them back and adding them where they are missing. —¿philoserf? (talk) 12:47, 21 June 2020 (EDT)

Language word templates

I am contemplating what each language’s word template should contain. Input welcome. See template:Vilani, template:Aslan, template:Vargr, template:Kkree, template:K'kree, template:Hiver, template:Gvegh , [[template:...]]. At the moment I have copied the Vilani template. I am however uncertain what it and the others should contain. I wonder if there should be a universal {{word|<foreign>|<anglic>|language}} Or {{word|language|<foreign>|<anglic>}} template. Or even, do we use cargo to build a universal translator {{word|from|to|<word>|>}}. That would look like {{word|vilani|anglic|!xeng'ri|>}} => !xeng'ri (Anglic: two legs).

—¿philoserf? (talk) 16:03, 22 June 2020 (EDT)

The original purpose of the Template:Vilani was an experiment to show off using CSS to display the Vilani bold font for some words. Rather than your more brilliant suggestion about including a formatted layout of translation for every word. If the dictionary entries are created correctly and according to the format I should be able to use the DPL/section transclusion to extract the translated word for display in the template. Let me experiment with this as an idea for a little while.

Don't kill yourself. Baby steps. Just having a convention for the other languages is an improvement. I'm still noodling it. —¿philoserf? (talk) 21:19, 22 June 2020 (EDT)

Do keep in mind there is no such language as "Vargr" (There are dozens of Vargr languages and dialects), "K'kree" (it should be !Kee), or "Hiver" (see Gurvin). Tjoneslo (talk) 20:27, 22 June 2020 (EDT)

Yep. Dusting some cobwebs outta the corners of my brainpan. —¿philoserf? (talk) 21:19, 22 June 2020 (EDT)

Under that reasoning category: Aslan dictionary should be category: Trokh dictionary. Perhaps I should make that change in the dictionary cleanup sub-subproject. —¿philoserf? (talk) 21:34, 22 June 2020 (EDT)

Yes, that is correct. Good Catch. Tjoneslo (talk) 22:17, 22 June 2020 (EDT)

And another thing that was broken, and now fixed. The Vilani displays correctly if you refresh the browser cache. Tjoneslo (talk) 20:56, 22 June 2020 (EDT)

I noticed when the Vilani showed up. Great job. —¿philoserf? (talk) 21:19, 22 June 2020 (EDT)

Extended UWP template

The SUB parser function now works! Sweet. I've seen what you've done with the Extended UWP template and it looks great.

I'm not sure what your plan was with the popup, but you can use a <span title="title"> tag to show a popup title (similar withholding the mouse over a link). Try putting your mouse over the text "popup title" in the previous sentence. We could either show a different popup with each character or create one big one for the entire UWP. Tjoneslo 15:17, 14 November 2007 (UTC)

I tried putting a span in the UWP (just for uc) and it made the entry disappear. Dcorrin 18:52, 14 November 2007 (UTC)

I'm using the expanded UWP format. The UWPexp template includes formatting, which confuses the <span title="">. I created a Template:UWPexpand without any formatting. I've discovered the title has no formatting capability (one line of plain text). I've found a CSS hack that may work and I'll put that in and see if it works any better. Tjoneslo 21:13, 14 November 2007 (UTC)

Review the User:tjoneslo/UWP page for an updated version of the UWP template. You may need to do a <shift>-reload to get the updated CSS code into your browser. If you hover over the UWP in the lower (example) template, it shows the entire Expanded UWP. We may need to shorten some of the text to let it fit. Tjoneslo 21:38, 14 November 2007 (UTC)

I had tried to just put in a <span title="test"> into the template and I still seemed to come up with the error. The CSS fix seems to work, but with the right justification on the template, the mouseover seems to go off the right end of the page. Dcorrin 16:26, 15 November 2007 (UTC)

The text generated by the Template: UWPexpand for the popup-display is too long for the box. I'm hesitant to put too much formatting in the template because the expanded template ends up on the page including the UWP template (just hidden via the CSS). I'll make the box a little narrower. But there may need to be a limit of 20-30 characters for each line.

Another problem: I've shifted to using one of the newer Quarz skins, which places all of the Wiki menus on the right side (the articles are up against the left edge of the screen. This means the infoboxes are about centered, and there is plenty of space to pop-up the extended UWP information over the Wikia menus (and advertising). I suspect you are still using the older Monobook skin (with the three columns). Let me try the older skin and see what it looks like. Tjoneslo 17:09, 15 November 2007 (UTC)

I've fixed the CSS box, it is now slightly smaller and centered under the UWP you have the mouse on. Take a look and see what you think Tjoneslo 17:18, 15 November 2007 (UTC)