User talk:Nikolaos~enwikisource

— billinghurst  sDrewth  08:52, 12 January 2012 (UTC)

about new lines in footnotes
Would you prefer a new line between items in Footnotes or no newline? I put a after each item so they run closely together. Let me know.

Sergius g (talk) 16:17, 14 January 2012 (UTC)


 * I haven't really thought about it, but the ones running closely together actually look better. I'll do mine with a &lt;br />. Nikolaos (talk) 00:53, 15 January 2012 (UTC)


 * Well, now that I've implemented it in my pages, I'm not sure any more. What would you think of a horizontal rule between each one? Nikolaos (talk) 01:00, 15 January 2012 (UTC)

css styles
we're probably at the right point to define the classes and styles we should use. I think we need to create css classes for:

1. Footnotes (for the div) 2. All tables with summary forms and phrases. 3. Exercises

As soon as we find out how to include our own css, we'll be cooking.

Sergius g (talk) 16:17, 14 January 2012 (UTC)


 * Let me know what you find out Nikolaos (talk) 00:54, 15 January 2012 (UTC)

highlight
Please see lesson 7 and tell me if you're OK with the color and the concept.

Re: Highlight
I like it. I'll see how it looks in longer remarks as well. Nikolaos (talk) 22:04, 16 January 2012 (UTC)


 * It looks a little odd in lessons 2 and 3, but not necessarily bad. Would you also like to do this for N.B. remarks?


 * I agree, looks a bit too bright, especially at the end of the day :) May be a lighter gray would work better, or very pale red. I think div's would better too than spans so that the color is continuous. If you are good with colors, I'll gladly follow on this one.

Sergius g (talk) 22:36, 16 January 2012 (UTC)

Em dashes
I've found that style guides recommend not putting a space before or after em dashes, and Adler seems to follow this convention himself. Do you want to follow this as well? Fixing existing articles would be as simple as searching and replacing instances of a dash with a space before and after it (as well as those with only a space before them) with the dash itself. Nikolaos (talk) 22:17, 16 January 2012 (UTC)


 * Yep, I think it would be closer to the original. I observed that in situations like :&mdash; but not elsewhere. If you could do it, it would be great. I'm still working on the CSS situation.

Sergius g (talk) 22:37, 16 January 2012 (UTC)

Lesson 9
Very interesting about the missing text. When I view it on Google in the browser, I do see the missing part but when I'm using evince, I don't. Too lazy to try it in Acrobat. Thank you for helping me out here.

Dictatae
Do you think we should group dictatae just like in the textbook? Right now, I've been creating a dictata page for each one. I'm kind of leaning toward several on one page. In that case the URL will be something like Dictata_10_11_12_13. Let me know.

Script

 * 1) !/bin/sh

echo " " IFS=$OLDIFS

I don't know if you'll find this useful. I found myself creating tables too many times. So... If in vim you type a series of lines of the form:

Text1[TAB]Text2[TAB]Text3_1@Text3_2@Text_3 Text1[TAB]Text2[TAB]Text3_1@Text3_2@Text_3 Text1[TAB]Text2[TAB]Text3_1@Text3_2@Text_3 ...

Then if you do a visual select in Vim, press ! and then enter the path the script, it will return an HTML table. If the first column is case names, it will put the triple wiki quotes around them. The @ signs will be replaced by br's. Saved me some time.

Table of contents
Take a look at lesson 13. I struggled with the table of contents for a long time. I think it makes sense to put the number of the lesson under "notes" in the header and put the actual title of it as the first thing in the table of contents. Lesson 13 is a good example of how deep the levels of the TOC can nest. Let me know if you're OK with this change

P.S. I've created some post-processing commands helpful for editing the exercises and the answers to them. The biggest help is putting macrons automatically in many "usual places". Let me know if you're interested and I'll post the script -- a sequence of vim commands really.

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Nikolaos. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Nikolaos~enwikisource that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:32, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 06:47, 21 April 2015 (UTC)