Re: carraMeL updated to v. 1001 2005-05-18 - By elsiget
Back
How about exchanging "evil" characters with -, and using something
similar to formatted printing in C (generics isn't that what it's
called?),
where you have a set of characters in a list that should be put in
there instead (that is, if '-' is a legal character, or else it could
be any other legal character, should that character be in the name
just replace it with itself in the replacement system)...
Caramel is used in english as well, but I believe toffee is a certain
type of caramel, or maybe it's the other way around...
So the play on words is quite valid in english as well, the filename
of course could be something like CML or CarML,
just to shorten the the extension...
--- In Carrara@(protected), nospam <nospam@(protected)> wrote:
> Bonjour Jasen,
>
> Before anything else, caramel is the French for toffee. Thus carraMeL,
> made of Carrara and Markup Language, but with an extra "e" inbetween.
> If you remove the "e" part of the play on words falls ;-)
>
> I a willing to participate in any effort to XMLize the .car format.
> Your help is welcome.
> I just won't do anything else than PHP myself, 'cause I have absolutly
> no time now to learn anything else with three children under age of 5
> (good luck to Petteri ! Hope he manages it better than me to share his
> time between Carrara and the family ...).
>
> Maybe we should move that threat to the Carrara SDK yahoo group,
> though (even if it is not related to the SDK, it is related to
> plug-ins) to avoid bothering the main list.
>
> I just quickly answer inline then move the thread to the SDK list
> (unless you disagree).
>
>
> JJ> The first thing that needs to be done is to generate well-formed
> JJ> XML. Right now the elements "ren:" and "ren;" are bad. The latter
> JJ> because it's invalid, the former because it's an improper use of
> JJ> the ":" character. I propose that the XML element name become <ren>
> JJ> with the fourth character becoming an attribute like <ren
> qualifier=";">>. Unfortunately, this doesn't handle the general case
> JJ> where there may be other elements that have invalid XML tag names,
> JJ> but I don't see any other than those two.
>
> I just requested a list of valid chars from Arnaud at Eovia.
> The attribute idea is a possibility ; another is just mapping the
> invalid chars to valid one. Use of attributes to discriminate elements
> name is not the best solution. Elements have meanings, attributes
> others. Also, would complicate Xptah queries.
>
> JJ> Next, are those elements that have multiple values after them like:
> JJ> WBC1 0.5,0.5,0.5. To be good XML, those values ought to be broken
> JJ> up into separate attributes like <WBC1 a="0.5" b="0.5" c="0.5"/>.
>
> Both systems are good XML. The text nodes must be parsed by a computer
> programm anyway, so it doesn't matter really if these are multiple
> values or single ones. A solution would be to use a CDATA section,
> juste like I did for, say, the bitmap shaders.
>
> JJ> Finally, is the "AdUV" element. Unlike every other item, this
> JJ> appears to have some qualifier immediately following it, with the
> JJ> values on the next line:
> JJ> AdUV 2
> JJ> 0.68986654,0,0.68986654,1
>
> yep, I discovered that when I uploaded the Carrara 1 file.
>
> JJ> It would be interesting to test whether the line breaks are
> JJ> significant, or if Carrara would parse correctly if all the values
> JJ> were on one line. Unfortunately, it presents a special case to the
> JJ> XMLizer: If the next line starts with a number then add it to the
> JJ> attributes of the current element - or somesuch.
>
> As far as I understand, there is a rule in .car file that prevent a
> line from including more than one blank space (except the ones at the
> begining of the line that are just for indentation and can be safely
trimed). carraMeL is largely
> based on that rule. I suppose it is also important for the Carrara
parser
> itself, and that explains that that special AdUV is splitted over two
> lines.
>
> Since Bob said C5 is far from now, it may be possible for them to
> just change their parser so that this syntax resolves to :
> AdUV {
> AdUVfirstVal 2
> AdUVsecondVal 0.68986654,0,0.68986654,1
>
> This would be just the most logical if they don't want to jump into
> the XML wagon themselves.
>
> JJ> FWIW, I use XML extensively at work - devising schemas, writing
> JJ> XSLT, etc. I'd be very happy to offer some expertise on this
> JJ> project. I'm in the middle of moving into a new house, so I don't
> JJ> know that I'll be able to provide any coding support, though.
>
> JJ> Good project. I hope it turns into something.
>
> It does not depends on me actually.
>
> JJ> - Jasen.
>
>
>
>
>
>
>
> --
> Cordialement / Sincerly yours,
> Fran�ois
> Flocons de P�ques
> Infographie 2D et 3D - Cr�ation web - Services informatiques
> www.floconsdepaques.com
>
>
> :=
> ,H:
> @/ ..
> -HH$. -===-,
> ;@(protected)= .=::=-,,
> /@(protected)$, .::::=-,
> $= .:;::::=,
> .XHHXX$:. -;;;;:::-,
> =HHHX$$/;;- -+/;;;:::=-
> =HHXX$/;:==, :+//;:::==-. .
> ,HHX$/;:=---, :///;;::=-,, ...
> +@(protected)$/;::=---,, ,///;;::=-,. ,,
> .$H$/::::=-,--, =/;;;::=-,, .,,.
> ,XH$/:==:=---==,..-/;;:::-,---,..,,
> ,$/;:====-- --=:--;/;:::;/==,=-,-,
> ./+;:=--=---,-,=;:=:/;//+$;=,/+,.,.
> =//:=-- --,---=;;,-;X/-:;-=:;;=,
> .:/;:=====----=;; .=$;::--;/X#+
> . ,:;::==::==--:;;:+//+$;%#X
> ./%/:==:;;::::::::=++:+H$X/.
> :$+$%+/++//;;;;/;:/X;$+/%H$-:+;
> %/;/+++++/+++++/;////M$/X#/X###@(protected)
> ,$;::;//////+++/::;/@@(protected)@@@@(protected)$H##=
> :X;:=-=:;;//;;:====::/+XHM@@@; ,.
> $/;:=-- ---- --,,-- ---=+@#M. /+
> -X$+/;::=-,,,,,--,,,,---==---+#X /,
> ;X;:=---,,,,,,,,,,,-,---==-;#/ ,:
> $/;:=--==-,,,,,.,,,-,,--==-#- ,
> ,X$+/:====-- ----,,,,,-- ----:#X ..=;////;:,.
> ,X$+;::==-- ---=-- --,-- --=;@#+ .;@(protected)@@(protected):.
> +$+;:=========--========:/X###+ ,+H@@@@@@@@@@@@(protected)@(protected)@(protected):-
> :+/::====::====::::::;;/@##M//
./H@@@@@@@@@@@(protected)@(protected)@(protected)@@(protected)+;
> -//;::::===:;;//;;;::=.##X.= -XM@@@@@@(protected)@@(protected)@@(protected)@@(protected)#@/
> ,=:;;///++///;:=-. :##= =H@@(protected)@@@@(protected)@(protected)@@(protected)@@@@(protected)#@/.
> .,--,,. :##- :MM@(protected)@@@(protected)@@(protected)@@@(protected)##$.
> :##- ,HM@(protected)@@(protected)@@(protected)@@(protected)#M:
> :#M- +@@@@@@(protected)@@@@@@(protected)@@(protected)#H-
> =MM-.XHH@(protected)@@(protected)@@@@@@(protected)
> -@@(protected)@@(protected)@@;
> -HH-=$$$$XXXXXX$$$XHXXXXHX=
> ,$X=-+%$%%%$X$$$$X,
> .$=,/+++++/+++%%++$/
> /+=,:;;;/;;;/++/////:
> :+:.:::::::;;/;;;;//-
> -;: =:--====;::::;;,
> ,==.,---,--:====::.
> .==..-,,,,-=---==
> -=, -,.,-=-,,--
> ,,, ,,..,-,,-,
> .,, .. .,.,,.
> ,, . ...,.
> ... . ...
> .
>
>
> Pi�ces jointes / Post-Joint : <none>.
Welcome Yahoo Members!
http://www.eovia.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/Carrara/
<*> To unsubscribe from this group, send an email to:
Carrara-unsubscribe@(protected)
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|
|
