On Apr 4, 8:09 pm, bjlhundrup <
mrleng...@gmail.com> wrote:
>
> I would help but in truth I know nothing of code or programming. But I
> do know how to make and what pecha should look like, for all that's
> worth.
Yup, that's definitely worth a lot :-)
Our teachers are often quite busy, so having someone available for
initial proofing and suggestions, discovering subtle layout (or other)
errors, will save us from having to bother lamas with those questions.
> If you plan to go so far as to make a new program I have ideas
> about a lot of needed thing like ornamental cover-pages. and there
> really does need to be support for images within the side brackets in
> the 'fancy-pages'
Yeah, actually, the current proposed solution is to address this more
generally with the use of "layers" -- this would allow folks to place
images anywhere they have a need. Of course, we'll want to provide
sensible defaults :-)
> And since we see each other now and again I will
> do what I can to help you!
Cool! Thanks :-)
> There is also
> much need for an extensive means for making custom page (as in paper)
> sizes.
Yeah, this is definitely part of the plan. That will come much later
in the process of the development, though -- as will most layout/
formatting oriented code. Initially we will be working on implementing
(and then tuning) the basic source abstractions, their interaction
with each other, as well as the basic user interaction options via the
GUI.
> Now I will end with saying that unless you truly make something
> perfect and complete, myself I don't see the need.
There are two needs: a functional one and an ideological need.
Firstly, PM doesn't provide a means for maintaining multiple sources
in their original files while simultaneously providing a means of
publishing pechas in a traditional format. In PM, once you add the
Tibetan, transliteration, and translation to the Pecha, they remain in
a combined form. If one person is in charge of maintaining the
Tibetan, and similarly the responsibilities for maintaining other
portions of the text rest with different individuals, you have a
process problem. Essentially, this means that in order to save time,
you must not make all edits in the .pxp file (or saved content file).
Any formating you want to do with just the source files themselves is
no longer possible (without redoing all the PM entry/copy/paste).
Secondly, PM is not open source. This is something that FWJ would also
like to see: an open source pecha editing/creating tool. Whether
PechaPublisher ends up being that tool or not, only time and effort
will tell.
> It should support every single Tibetan
> font out there,
Well, I can't guarantee *every* Tibetan font ;-) But I can't imagine
writing a tool that didn't use the best ones available. I fully intend
that PechaPub will support all the fonts that PM does.
> PP and PM really need to
> be inter useable
Yeah, that's also fully intended. Exactly how that pans out will
depend upon the implementation we settle on for PechaPub, so it's far
to early to make any statements about that. But having worked with
software all my life (both as a user and developer), I would never
dream of not offering users some acceptable means of migration/
compatibility.
Thanks for your email, Lhundrup!
d