Comments for WeSay Development Progress http://www.wesay.org/blogs Fri, 05 Dec 2008 10:17:09 +0000 http://wordpress.org/?v=2.6.5 Comment on Using WeSay from other applications by John Hatton http://www.wesay.org/blogs/2008/01/16/using-wesay-from-other-applications/#comment-2129 John Hatton Thu, 18 Sep 2008 03:40:02 +0000 http://www.wesay.org/blogs/2008/01/16/using-wesay-from-other-applications/#comment-2129 Mike, It's possible that FLEx isn't properly escaping the links when it outputs. Can you import that same file into a new FLEx instance? E.g., does FLEx like the file but WeSay doesn't? >I should also note that when I do put in hyperlinks (like jumps to FieldWorks views) those import with no error but when the file is written back out they have been stripped off so these links are lost and carriage returns are inserted Mike, can you clarify in what program each of the verbs here happen? In what program do you put hyperlinks? In what program do you import? Etc. Thanks Mike,
It’s possible that FLEx isn’t properly escaping the links when it outputs. Can you import that same file into a new FLEx instance? E.g., does FLEx like the file but WeSay doesn’t?

>I should also note that when I do put in hyperlinks (like jumps to FieldWorks views) those import with no error but when the file is written back out they have been stripped off so these links are lost and carriage returns are inserted

Mike, can you clarify in what program each of the verbs here happen? In what program do you put hyperlinks? In what program do you import? Etc.

Thanks

]]> Comment on Using WeSay from other applications by Mike Cochran http://www.wesay.org/blogs/2008/01/16/using-wesay-from-other-applications/#comment-2123 Mike Cochran Wed, 17 Sep 2008 17:33:00 +0000 http://www.wesay.org/blogs/2008/01/16/using-wesay-from-other-applications/#comment-2123 I have been using FieldWorks Flex with WeSay and things are working quite well. The export from FieldWorks is reasonable. The import is very slow. FieldWorks can now pick up the pictures from WeSay and on my import of the Biatah data it worked flawlessly. I was able to make changes in FLEx and they appeared in the WeSay data. I could go back and forth. I did run into a problem when I inserted a link from Libronix in my data and got the following error when I attemted to export from FLEx into WeSay : Could not build caches. There is a problem with the format of C:\Users\cochran\Documents\WeSay\WeSay bug\WeSay bug.lift. Invalid attribute value is found. Value = 'file://libronixdls:jump|pos=LLS-AOL%3A5823%3CNLT.JN.1%3E.0.0|ref=bible.64.1.1|res=LLS%3A1.0.171' Expected attributes are: .file:///C:/Users/cochran/Documents/WeSay/WeSay bug/WeSay bug.lift line 77, column 8 Error near: href 'file://libronixdls:jump|pos=LLS-AOL%3A5823%3CNLT.JN.1%3E.0.0|ref=bible.64.1.1|res=LLS%3A1.0.171' I should also note that when I do put in hyperlinks (like jumps to FieldWorks views) those import with no error but when the file is written back out they have been stripped off so these links are lost and carriage returns are inserted I have been using FieldWorks Flex with WeSay and things are working quite well. The export from FieldWorks is reasonable. The import is very slow. FieldWorks can now pick up the pictures from WeSay and on my import of the Biatah data it worked flawlessly. I was able to make changes in FLEx and they appeared in the WeSay data. I could go back and forth.

I did run into a problem when I inserted a link from Libronix in my data and got the following error when I attemted to export from FLEx into WeSay :
Could not build caches. There is a problem with the format of C:\Users\cochran\Documents\WeSay\WeSay bug\WeSay bug.lift. Invalid attribute value is found. Value = ‘file://libronixdls:jump|pos=LLS-AOL%3A5823%3CNLT.JN.1%3E.0.0|ref=bible.64.1.1|res=LLS%3A1.0.171′ Expected attributes are: .file:///C:/Users/cochran/Documents/WeSay/WeSay bug/WeSay bug.lift line 77, column 8
Error near: href ‘file://libronixdls:jump|pos=LLS-AOL%3A5823%3CNLT.JN.1%3E.0.0|ref=bible.64.1.1|res=LLS%3A1.0.171′

I should also note that when I do put in hyperlinks (like jumps to FieldWorks views) those import with no error but when the file is written back out they have been stripped off so these links are lost and carriage returns are inserted

]]> Comment on Using Python To Read a FieldWorks Lexicon by Craig http://www.wesay.org/blogs/2006/12/29/using-python-to-read-a-fieldworks-lexicon/#comment-1854 Craig Thu, 31 Jul 2008 07:30:33 +0000 http://www.wesay.org/blogs/2006/12/29/using-python-to-read-a-fieldworks-lexicon/#comment-1854 A few things have changed since this original post. I've put some updated example code here: http://groups.google.com/group/flex-list/web/using-python-to-access-a-flex-database A few things have changed since this original post. I’ve put some updated example code here: http://groups.google.com/group/flex-list/web/using-python-to-access-a-flex-database

]]> Comment on WeSay Action Addins by prandin http://www.wesay.org/blogs/2007/05/17/wesay-action-addins/#comment-1443 prandin Thu, 10 Jul 2008 01:42:09 +0000 http://www.wesay.org/blogs/2007/05/17/wesay-action-addins/#comment-1443 Thanks you a lot for your site. Really really helpfull for my project! Thanks you a lot for your site. Really really helpfull for my project!

]]> Comment on Multiscribe by Andrew http://www.wesay.org/blogs/2007/01/05/multiscribe/#comment-764 Andrew Mon, 14 Apr 2008 01:56:25 +0000 http://www.wesay.org/blogs/2007/01/05/multiscribe/#comment-764 I was wondering how far you had progressed with Multiscribe. Is there a working version? and which applications does it currently work with? Andj. I was wondering how far you had progressed with Multiscribe. Is there a working version? and which applications does it currently work with?

Andj.

]]> Comment on Multiscribe by Anonymous http://www.wesay.org/blogs/2007/01/05/multiscribe/#comment-380 Anonymous Tue, 15 Jan 2008 12:33:13 +0000 http://www.wesay.org/blogs/2007/01/05/multiscribe/#comment-380 <p>Multiscribe should be excellent point after you did miraculously; thank you much!</p> Multiscribe should be excellent point after you did miraculously; thank you much!

]]> Comment on Simple and Advanced Sorting by Palaso » Blog Archive http://www.wesay.org/blogs/2007/11/12/simple-and-advanced-sorting/#comment-378 Palaso » Blog Archive Mon, 14 Jan 2008 09:46:45 +0000 http://www.wesay.org/blogs/2007/11/12/simple-and-advanced-sorting/#comment-378 [...] part of implementing our strategy for simplified sorting rules I needed to write a parser for the rules. Of course I started out looking at parser generators but [...] [...] part of implementing our strategy for simplified sorting rules I needed to write a parser for the rules. Of course I started out looking at parser generators but [...]

]]> Comment on Our first OLPC by John http://www.wesay.org/blogs/2007/04/19/our-first-olpc/#comment-171 John Thu, 19 Apr 2007 08:55:15 +0000 http://www.wesay.org/blogs/2007/04/19/our-first-olpc/#comment-171 Wow, I would like one of those... Wow, I would like one of those…

]]> Comment on Multi-lingual Option Lists by Eric Albright http://www.wesay.org/blogs/2007/01/26/multi-lingual-option-lists/#comment-51 Eric Albright Wed, 21 Mar 2007 15:40:57 +0000 http://www.wesay.org/blogs/2007/01/26/multi-lingual-option-lists/#comment-51 The tags for identifying languages should conform to <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt" rel="nofollow">BCP 47</a>. The shortest <a href="http://en.wikipedia.org/wiki/ISO_639" rel="nofollow">ISO 639</a> code is preferred. It is true that for most languages, they will need to use a three letter code. We are hoping to have a tool that will help users create these codes in a friendly way so that they won't have to read standards documentation to figure out what code they should be using. The tags for identifying languages should conform to BCP 47. The shortest ISO 639 code is preferred.

It is true that for most languages, they will need to use a three letter code. We are hoping to have a tool that will help users create these codes in a friendly way so that they won’t have to read standards documentation to figure out what code they should be using.

]]> Comment on Multi-lingual Option Lists by jim albright http://www.wesay.org/blogs/2007/01/26/multi-lingual-option-lists/#comment-50 jim albright Wed, 21 Mar 2007 13:39:46 +0000 http://www.wesay.org/blogs/2007/01/26/multi-lingual-option-lists/#comment-50 I see that your writing systems all use the 2-letter abbreviation. Why not start using the 3-letter abbreviation. The linguist will have to for their own language. I see that your writing systems all use the 2-letter abbreviation. Why not start using the 3-letter abbreviation. The linguist will have to for their own language.

]]>