> Can you upload the entire log somewhere?
>
Here it is (a 22.9 MB file):
https://dl.dropboxusercontent.com/u/8293746/log-compiling-sage68-osx10.11-beta3.txt
>
> It seems that you made it to the documentation build, so ./sage should
> work (probably crashes but possibly with an informative
I am not so sure about the needed "localization"...
Yes, could be the docstrings (= the text used as comment in various parts
of SAGE python component)in that case, I guess as a python newbee, you
have python tool for extract text comments from code and polib to merge
them all in text fil
Can you upload the entire log somewhere?
It seems that you made it to the documentation build, so ./sage should work
(probably crashes but possibly with an informative error message)
On Wednesday, August 5, 2015 at 8:55:54 PM UTC+2, Juan Luis Varona wrote:
>
> Thanks for the answer. As suggeste
Thanks for the answer. As suggested, I have tried to compile Sage 6.7 and
6.8 from source in Mac OS X 10.11 (El Capitan) public betas 1, 2 and 3,
without success.
This is the final message of the process of compilation with sage 6.8 with
Mac OS X 10.11 public beta 3:
Well there isn't much tooling (since one rarely wants to translate
docstrings), but its easy to programmatically extract docstrings. Then just
write them out in a pofile, translate, and change ? to look up the
translation.
--
You received this message because you are subscribed to the Google G
On Wed, Aug 5, 2015 at 8:41 AM, kcrisman wrote:
> Surely this is far too late but as I think you know from other stuff (you
> are the one contributing this, I believe) the sagenb can be localized, Sage
> proper does not (yet) have any facility for doing so.
>
There's a (depressing) discussion abo
Surely this is far too late but as I think you know from other stuff (you
are the one contributing this, I believe) the sagenb can be localized, Sage
proper does not (yet) have any facility for doing so.
I have an idea to create Ukrainian localization of Sage. It will be useful
> for many Ukrai
You could zoom in (control plus) the browser window, which should be
> equivalent for testing purposes.
>
>
>
That's what we ended up telling my students.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop
> One thing I didn't like was the inability to hide the contents frame(?) on
>> the left-hand side. It just sits there for no good reason, and is a
>> distraction.
>> IMHO it should automatically hide itself...
>>
>
> Yes, we discussed that one a lot. Try slowly making your browser window
>
On Wed, Aug 5, 2015 at 3:00 AM, dimpase wrote:
>
>
> On Wednesday, 5 August 2015 00:20:02 UTC+1, Rob Beezer wrote:
>>
>>
>> On Sunday, August 2, 2015 at 1:12:29 AM UTC-7, Dima Pasechnik wrote:
>>>
>>> One thing I didn't like was the inability to hide the contents frame(?)
>>> on the left-hand side
On Wednesday, 5 August 2015 00:20:02 UTC+1, Rob Beezer wrote:
>
>
> On Sunday, August 2, 2015 at 1:12:29 AM UTC-7, Dima Pasechnik wrote:
>
>> One thing I didn't like was the inability to hide the contents frame(?)
>> on the left-hand side. It just sits there for no good reason, and is a
>> dist
Since we aready have a private .ipython-* directory I'm fine with using the
profile_default in there.
On Wednesday, August 5, 2015 at 4:23:00 AM UTC+2, Kwankyu Lee wrote:
>
> Hi,
>
> As of version 6.8, Sage seems to read "profile_default" in
> $DOT_SAGE/ipython-* directory by default. As I reme
12 matches
Mail list logo
