[Latingp] Fwd: Transfer of List of Codepoints to Google Docs

[Emblen-Jarrett, Scott]

Dear colleagues,

My Google account is ubique1914 at googlemail.com. I've already added some information about the use of ? in Saanich; what would I need as "proof of attestation" for the use of this symbol?
I will be able to look through and contribute throughout the next couple of weeks.

Best wishes

Scott

________________________________
From: latingp-bounces at icann.org <latingp-bounces at icann.org> on behalf of Mirjana Tasic <Mirjana.Tasic at rnids.rs>
Sent: 11 June 2016 19:23:09
To: Meikal Mumin; LatinGP at icann.org
Subject: Re: [Latingp] Fwd: Transfer of List of Codepoints to Google Docs


Dear colleagues,

My google account is


tasmirjana at gmail.com


We have used Google docs in some other working group, it is friendly tool, easy to use.


I am sorry, I cannot dedicate some more time to our work now, I have first free slot at the end of July, during my holiday.


Regards Mirjana.

________________________________
Od: latingp-bounces at icann.org <latingp-bounces at icann.org> u ime korisnika Meikal Mumin <meikal.mumin at uni-koeln.de>
Poslato: 11. jun 2016. 15:56
Za: LatinGP at icann.org
Tema: [Latingp] Fwd: Transfer of List of Codepoints to Google Docs


---------- Forwarded message ----------
From: Meikal Mumin <meikal.mumin at uni-koeln.de<mailto:meikal.mumin at uni-koeln.de>>
Date: 8 June 2016 at 23:53
Subject: Transfer of List of Codepoints to Google Docs
To: LatinGP at icann.org<mailto:LatinGP at icann.org>


Dear colleagues,

since Chris has left us I thought it was a good moment to try and transfer our work into a form which is better suited for collaboration. I for one was having problems with the Word files, which were very slow and kept crashing for me, plus keeping the versions apart was confusing to me.

Accordingly, when I found some time to continue the review of the list codepoints I had promised earlier, I took the time to convert it into a Google Docs Spreadsheets documents, which is like an Excel file but stored in the cloud and it can be edited in the browser. All changes are tracked and saved automatically, so ideally we can stop worrying about version control.

I am still in the progress of walking through the list of codepoints. However I'm sharing it with you now so we can continue collaborating on it while I go on with my own review. We can always export the work from their back to an Excel or any other spreadsheet file (including all earlier versions under automatic version control) should the need arise. It offers nearly all other features of Excel, including features such as comments and highlights we all know from Word.

You can access the document from any browser using this link:
https://docs.google.com/spreadsheets/d/1FX5XEuqU2g5-pVr6rWLRhE3KiE4JxT8Kd70I6jlMSBU/edit?usp=sharing

If you have any Google Account it would be good to access the document while you are logged in, so we could all understand who made comments and changes, however it is not necessary for access. Please let me know if you have any Google (Apps) account so I could invited you directly to edit and take ownership of the document (currently it is associated with my own Google account) so it will become accessible to all LGP members and so we could share the administration of our repository of documents also in the future.

Similarly and again for the sake of simplicity of collaboration, I plan to transfer the draft for the actual proposal from Word into a Google Docs Text document.

I hope this will prove helpful and enable us to collaborate easier and make some progress, even during our transitioning period from one chair to another (set of) chairs.

I'll look forward to any comments either on the conversion process or the documents themselves.

Best wishes,

Meikal

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/latingp/attachments/20160611/f704a69b/attachment-0001.html>