Conrad Irwin wrote:
> On 03/31/2010 12:31 PM, Victor wrote:
>> Hi, now I see...
>>
>> I've posted a message to the fa.caml newsgroup:
>> http://groups.google.com/group/fa.caml/browse_frm/thread/1593e053759d7679
>>
>> hopefully somebody will volunteer to fix the issues, thus
>> saving the human reso
On 30 March 2010 15:34, Victor wrote:
> On Tue, 30 Mar 2010 16:05:02 +0300, David Gerard wrote:
>> Getting it off Ocaml is an excellent first step. I have tried and
>> failed to get texvc working properly in MediaWiki myself more than a
>> few times, because of Ocaml not wanting to play nice ...
2010/3/31 Daniel Schwen :
>> ([8, 32, 189].sort()[0]) === (new Boolean(false) ? 189 : 8)
>
> Why such a contrived example?! This all boils down to
>
> new Boolean(false) == false
> returning true
>
> new Boolean(false) === false
> returning false
>
Not quite. There's also the issue of [8, 32, 189].
> ([8, 32, 189].sort()[0]) === (new Boolean(false) ? 189 : 8)
Why such a contrived example?! This all boils down to
new Boolean(false) == false
returning true
new Boolean(false) === false
returning false
The ?: operator is just not performing an implicit cast. The fact that
the Boolean object i
On 03/31/2010 05:32 PM, Daniel Schwen wrote:
>> I could be worse, It could be Math in Javascript:
>> v = (011 + "1" + 0.1)/3;
>> 303.36667
>
> Somebody ought to slap you for mixing four different types in such a
> horrendous manner to construct something that is supposed to make
> people
> I could be worse, It could be Math in Javascript:
> v = (011 + "1" + 0.1)/3;
> 303.36667
Somebody ought to slap you for mixing four different types in such a
horrendous manner to construct something that is supposed to make
people who do not understand octal numbers and string concatenat
On Wed, Mar 31, 2010 at 14:24, Tei wrote:
> Doing Math in any programming language or digital computer is a bad
> idea. Anyway.
The texvc component doesn't "do math". It just sanitizes LaTeX and
passes it off to have a PNG generated from it.
___
Wikite
On 30 March 2010 16:34, Victor wrote:
>>
>> Getting it off Ocaml is an excellent first step. I have tried and
>> failed to get texvc working properly in MediaWiki myself more than a
>> few times, because of Ocaml not wanting to play nice ...
>
>
> Actually I completely disagree. Since I've go
On 03/31/2010 12:31 PM, Victor wrote:
>
> Hi, now I see...
>
> I've posted a message to the fa.caml newsgroup:
> http://groups.google.com/group/fa.caml/browse_frm/thread/1593e053759d7679
>
> hopefully somebody will volunteer to fix the issues, thus
> saving the human resources for better tasks.
On Wed, 31 Mar 2010 13:58:03 +0300, Ævar Arnfjörð Bjarmason
wrote:
> On Tue, Mar 30, 2010 at 14:34, Victor wrote:
>> Actually I completely disagree. Since I've got some experience with both
>> OCaml and PHP the idea to convert Maths processing to PHP looks
>> like a not so good idea at all.
>>
Ævar Arnfjörð Bjarmason wrote:
> On Wed, Mar 31, 2010 at 10:58, Ævar Arnfjörð Bjarmason
> wrote:
>> c is "better"
>
> That should have been "OCaml".
No it shouldn't! :)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedi
On Wed, Mar 31, 2010 at 10:58, Ævar Arnfjörð Bjarmason wrote:
> c is "better"
That should have been "OCaml".
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Mar 30, 2010 at 14:34, Victor wrote:
> Actually I completely disagree. Since I've got some experience with both
> OCaml and PHP the idea to convert Maths processing to PHP looks
> like a not so good idea at all.
>
> Probably the issues you had were more like a wrong/problematic
> configura
On Tue, 30 Mar 2010 16:05:02 +0300, David Gerard wrote:
> On 23 March 2010 19:17, Rob Lanphier wrote:
>
>> As I'm sure you've already gathered from the other responses, this is
>> exactly the right place. I'm a little skeptical myself that porting
>> that
>> particular piece of code from OCam
Bryan Tong Minh wrote:
> On Tue, Mar 30, 2010 at 2:13 PM, Platonides wrote:
>> Changing to python will also break for people that compiled math, update
>> without reading the release notes and don't have python.
>>
> While this is ofcourse possible, how big is the chance that somebody
> will have o
* Bryan Tong Minh [Tue, 30 Mar 2010 17:22:09
+0200]:
> While this is ofcourse possible, how big is the chance that somebody
> will have ocaml but not python?
>
Fedora Linux has ocaml for ages. yum install ocaml or something like
that. Compiling texvc is fast and easy - never had any problems. Si
On Tue, Mar 30, 2010 at 2:13 PM, Platonides wrote:
> Changing to python will also break for people that compiled math, update
> without reading the release notes and don't have python.
>
While this is ofcourse possible, how big is the chance that somebody
will have ocaml but not python?
_
On 29 March 2010 01:12, Aryeh Gregor wrote:
>> I have never built a wiki
>> where texvc has been needed, wanted, or even thought harmless.
> Granted, this is not as widely used as some other optional features.
> There are certainly many wikis that do use it, though -- it's not like
> no one will
On 23 March 2010 23:19, K. Peachey wrote:
> On Wed, Mar 24, 2010 at 9:16 AM, Trevor Parscal
> wrote:
>> I think we should really consider LOLCODE for this sort of thing.
>> http://en.wikipedia.org/wiki/Lolcode
>> It's just more fun!
> Also rewrite parser functions to use it? that would be inte
On 23 March 2010 19:17, Rob Lanphier wrote:
> As I'm sure you've already gathered from the other responses, this is
> exactly the right place. I'm a little skeptical myself that porting that
> particular piece of code from OCaml to Python is going to be a really big
> win for us (because it's st
Damon Wang wrote:
> Option (2) is the most maintainable and feasible option, and it's
> precisely the one that cannot be done in PHP. As far as I know, PHP has
> no parser-generator package. (Please, please let me know if that's
> incorrect so I can stop embarrassing myself and get on with writing
Aryeh Gregor wrote:
> On Mon, Mar 29, 2010 at 12:46 PM, Chad wrote:
>> What if it was written as an extension and moved to /extensions?
>> Then we get the benefit of decoupling Math from the core software,
>
> What benefit is this? It's not realistically decoupled from the core
> software unless
On Mon, Mar 29, 2010 at 12:46 PM, Chad wrote:
> What if it was written as an extension and moved to /extensions?
> Then we get the benefit of decoupling Math from the core software,
What benefit is this? It's not realistically decoupled from the core
software unless it avoids using MediaWiki fun
On Mon, Mar 29, 2010 at 12:12 PM, Aryeh Gregor
wrote:
> On Sun, Mar 28, 2010 at 11:45 PM, Damon Wang wrote:
>> Can we make update.php ask the user if he wants to install the new extension?
>
> That would be hacky and unreliable. We'd have to make sure the
> versions match, automatically alter Lo
On Sun, Mar 28, 2010 at 11:45 PM, Damon Wang wrote:
> Can we make update.php ask the user if he wants to install the new extension?
That would be hacky and unreliable. We'd have to make sure the
versions match, automatically alter LocalSettings.php (!), hope that
the wiki files are writable to t
> If you make sure to run update.php, it's very rare for your wiki to
> break, unless you've hacked things or not updated your extensions or
> such. We're usually pretty careful to avoid significant regressions
> when upgrading wikis that are using supported/sane configurations.
Can we make updat
On Sun, Mar 28, 2010 at 7:10 PM, Happy-melon wrote:
> As opposed to their wiki breaking when they upgrade for all the other
> reasons that we document in the release notes?
If you make sure to run update.php, it's very rare for your wiki to
break, unless you've hacked things or not updated your e
"Aryeh Gregor" wrote in message
news:7c2a12e21003281059i551c4650p8a8e51e100b62...@mail.gmail.com...
> On Fri, Mar 26, 2010 at 10:48 PM, Damon Wang
> wrote:
>> (You also as a Mediawiki extension rather than a core feature; I'm going
>> to do that, but I won't say anything more because it seems
On 28/03/10 18:59, Aryeh Gregor wrote:
> On Fri, Mar 26, 2010 at 10:48 PM, Damon Wang wrote:
>
>> (You also as a Mediawiki extension rather than a core feature; I'm going
>> to do that, but I won't say anything more because it seems fairly
>> uncontroversial.)
>>
> I actually disagree wi
On Fri, Mar 26, 2010 at 10:48 PM, Damon Wang wrote:
> (You also as a Mediawiki extension rather than a core feature; I'm going
> to do that, but I won't say anything more because it seems fairly
> uncontroversial.)
I actually disagree with this pretty strongly. It would be a
regression in functi
On Fri, Mar 26, 2010 at 7:48 PM, Damon Wang wrote:
> > There's a few Python-based things that might be interesting, but I
> > think you'll get a lot more love for doing something in PHP or C.
> > Since this is a student internship, you shouldn't be bashful about
> > using this as a learning oppo
> There's a few Python-based things that might be interesting, but I
> think you'll get a lot more love for doing something in PHP or C.
> Since this is a student internship, you shouldn't be bashful about
> using this as a learning opportunity.
>
> I'd only caution against convincing yourself (an
Aryeh Gregor wrote:
> As long as the worst that could happen on a large majority of
> installations is DoS, I don't think we should be afraid to rewrite the
> code just because *maybe* it would be less secure. We should
> obviously check over the new code carefully, but I wouldn't say it's
> any m
On Wed, Mar 24, 2010 at 10:43 AM, Conrad Irwin
wrote:
> Yes, \openout, \write, \closeout, \openin, \read, \closein. The infamous
> one is \write18, 18 is a special file descriptor that just executes
> shell commands, you can also use \openin={|}.
>
> People have noticed this problem, so some distr
> Even if it were not possible to break out of restricted write18, there
> will exist installations with write18 enabled, and I can't imagine
> people remembering to check. Depending on the flavour of LaTeX in use it
If people won't remember, surely either the MediaWiki installer or the
extension
On 03/24/2010 02:00 PM, Aryeh Gregor wrote:
> On Tue, Mar 23, 2010 at 6:28 PM, Conrad Irwin
> wrote:
>> Many LaTeX installations can be made read/write/execute anything by
>> default.
>
> What does that mean? LaTeX can invoke external programs? Using what
> commands? Is this functionality act
On Tue, Mar 23, 2010 at 6:28 PM, Conrad Irwin
wrote:
> Many LaTeX installations can be made read/write/execute anything by
> default.
What does that mean? LaTeX can invoke external programs? Using what
commands? Is this functionality actually enabled in practice in stock
LaTeX installs?
_
On Tue, Mar 23, 2010 at 9:06 AM, Damon Wang wrote:
> Hello everyone,
>
> I'm interested in porting texvc to Python, and I was hoping this list
> here might help me hash out the plan. Please let me know if I should
> take my questions elsewhere.
>
If I understand correctly, you want to write a
scr
Is my impression that this is a problem where a PHP implementation
could be better. Who cares if is slow? the result can be cache
forever?, is something you will run only once, and the heavyweight
work (draw) will be made by C compiled code like the GD library?.
you need speed in stuff that run in
On 03/23/2010 10:44 PM, Tim Starling wrote:
> Just because a language is context-sensitive doesn't mean it will be
> hard to write a parser for it. That's just a myth propagated by
> computer scientists who, strangely enough given their profession, have
> a disdain for the algorithm as a descripti
Happy-melon wrote:
> I took it to mean that he wanted to split the math parsing out as a
> **MediaWiki** extension, implementing as a parser tag hook in the
> usual way. Which is definitely highly desirable.
>
> --HM
Making it a MediaWiki extension is of course desirable (moving texvc out
of
"Platonides" wrote in message
news:hobfpi$4u...@dough.gmane.org...
> You seem to be thinking about creating a PHP extension. I don't think
> you should go that route. A binary is good enough, we don't need it to
> be in a PHP extension. That glue could be added later if needed, but
> would incre
On Tue, Mar 23, 2010 at 2:00 PM, Damon Wang wrote:
> I've been writing projects
> for university and for a computer lab I work at, but it's mostly small,
> one-off sysadmin things and usually the emphasis is more on "xyz server
> has to be back up before we open tomorrow" than writing good, clean
On Wed, Mar 24, 2010 at 9:16 AM, Trevor Parscal wrote:
> I think we should really consider LOLCODE for this sort of thing.
>
> http://en.wikipedia.org/wiki/Lolcode
>
> It's just more fun!
>
> - Trevor
Also rewrite parser functions to use it? that would be interesting on
en.wiki since they are alwa
I think we should really consider LOLCODE for this sort of thing.
http://en.wikipedia.org/wiki/Lolcode
It's just more fun!
- Trevor
On 3/23/10 3:44 PM, Tim Starling wrote:
> Conrad Irwin wrote:
>
>> On 03/23/2010 05:23 PM, Aryeh Gregor wrote:
>>
>>> On Tue, Mar 23, 2010 at 1:00 PM, Ro
Conrad Irwin wrote:
> On 03/23/2010 05:23 PM, Aryeh Gregor wrote:
>> On Tue, Mar 23, 2010 at 1:00 PM, Roan Kattouw wrote:
>>> DFAs parse regular languages, which means those languages can also be
>>> expressed as regexes. In fact, the regexes accepted by the preg_*()
>>> functions allow certain ex
Python is a nice language. PHP (portability) or C/C++ (speed) would be
better but Python is preferable to OCaml.
You mention ANTLR, something like that could be a good because it should
allow to generate the same parser in a different language with not so
much effort (probably you won't have enoug
On 03/23/2010 05:23 PM, Aryeh Gregor wrote:
> On Tue, Mar 23, 2010 at 1:00 PM, Roan Kattouw wrote:
>> DFAs parse regular languages, which means those languages can also be
>> expressed as regexes. In fact, the regexes accepted by the preg_*()
>> functions allow certain extensions to the language
Hello Rob,
> Just to be really clear, I'm not looking for a "right" answer on any of
> those questions. It's not necessary for you to be even interested in
> getting deeply involved in the Wikipedia user community to have a really
> successful project. The purpose of this line of questions is to
Hi Damon,
Thank you so much for floating your GSoC ideas early here on the mailing
list! Putting out concrete examples we can weigh in on is really helpful,
and engaging in this way is a fantastic way of demonstrating how you'll be
able to engage with us if we select your project.
On Tue, Mar 2
2010/3/23 Roan Kattouw :
> 2010/3/23 Aryeh Gregor :
>> This much I know, but is LaTeX actually a regular language?
>>
> I don't know; I was just making the point that writing a DFA parser in
> PHP is probably not very useful.
Sorry, I got confused and wrote DFA when I should have written LALR.
DFA
2010/3/23 Aryeh Gregor :
> This much I know, but is LaTeX actually a regular language?
>
I don't know; I was just making the point that writing a DFA parser in
PHP is probably not very useful.
Roan Kattouw (Catrope)
___
Wikitech-l mailing list
Wikitech-
On Tue, Mar 23, 2010 at 1:00 PM, Roan Kattouw wrote:
> DFAs parse regular languages, which means those languages can also be
> expressed as regexes. In fact, the regexes accepted by the preg_*()
> functions allow certain extensions to the language theory definition
> of regular expressions, allowi
On 03/23/2010 05:00 PM, Roan Kattouw wrote:
>>> I suggested a Python port because
>>>http://www.mediawiki.org/wiki/Summer_of_Code_2010#MediaWiki_core
>>> lists it as a potential project idea. I was under the impression that
>>> people around here did not want to leave texvc in OCaml. Is this
2010/3/23 Aryeh Gregor :
>> I've never used PHP for real programming, but how difficult would it be
>> to write a really simple, stupid first pass at a DFA parser? I suspect
>> I'd need much more than three months to make it useful, but would it be
>> possible to implement some coherent subset of t
On Tue, Mar 23, 2010 at 4:06 AM, Damon Wang wrote:
> I'm interested in porting texvc to Python, and I was hoping this list
> here might help me hash out the plan. Please let me know if I should
> take my questions elsewhere.
Python is much better than OCaml, and I prefer Python to PHP, but a
PHP
Hello Conrad,
>> 2. Implement an AMS-TeX validator
>
> How different would this be from the current validator?
It should be exactly the same, except written in Python.
>> 5. Repackage the entire Math thing as an extension
>> I might do this if I have time left at the end. I'm sure the project
>>
2010/3/23 Conrad Irwin :
> Instead of rewriting the parser, it might be more productive to
> create parsers for some of the other languages that extensions use,
> hopefully with a view to adding additional extensions to Wikipedia. The
> ones I can think of immediately are tags (bug 3252/5856),
>
On 03/23/2010 08:06 AM, Damon Wang wrote:
> Hello everyone,
>
> I'm interested in porting texvc to Python, and I was hoping this list
> here might help me hash out the plan. Please let me know if I should
> take my questions elsewhere.
>
> Roughly, my plan of attack would be something like this:
Hello everyone,
I'm interested in porting texvc to Python, and I was hoping this list
here might help me hash out the plan. Please let me know if I should
take my questions elsewhere.
Roughly, my plan of attack would be something like this:
1. Collect test cases and write a testing script
Thanks
60 matches
Mail list logo
