David Blue (Mailing List Addy) wrote:
On Friday 10 March 2006 23:29, Kahunapule Michael Johnson wrote:
I am not a religious follower of open source and ISO standards. Actually, I
care little about ISO endorsement of any standard unless the standard is
both relevant to the task at h
Martin Gruner wrote:
Besides, it gave a working solution while I waited for
OpenOffice.org Writer to gain OpenDocument text format support, and while
I'm still waiting for SIL Graphite support to be added to OOo.
Oh! I didn't know that SIL Graphite was already incorporated in
> Besides, it gave a working solution while I waited for
> OpenOffice.org Writer to gain OpenDocument text format support, and while
> I'm still waiting for SIL Graphite support to be added to OOo.
Oh! I didn't know that SIL Graphite was already incorporated into MS products.
mg
_
On Friday 10 March 2006 23:29, Kahunapule Michael Johnson wrote:
> I am not a religious follower of open source and ISO standards. Actually, I
> care little about ISO endorsement of any standard unless the standard is
> both relevant to the task at hand and a better solution than reasonable
> alter
Jonathon Blake wrote:
Kahuna pule Michael wrote:
program that reads Unicode USFM Scripture files and produces a Microsoft Word 2003 XML (WordML) document
Given your desire for open standards, why does it produce output for a
non-standard, proprietary, closed file format
Kahuna pule Michael wrote:
> program that reads Unicode USFM Scripture files and produces a Microsoft Word
> 2003 XML (WordML) document
Given your desire for open standards, why does it produce output for a
non-standard, proprietary, closed file format?
Especially when there is a European File
The manual has now been posted on the bibletechnologies.net home page
along with the schema.
The and elements now have a marker attribute for the
specific quotation mark, which will satisfy markup needs.
For a continuation quotation marker n="""/> can be used, where the attribute n contains the
Kahunapule Michael Johnson wrote:
Apparently, amending the documentation to reflect those changes and
openly publishing the results has not been a high priority.
This change, once fully implemented in documentation and properly
published, would elevate OSIS from unusable without modification to
Chris Little wrote:
> Kahunapule Michael Johnson wrote:
>> First, please let me apologize. By the personal attacks in your message,
>> you may have gotten the impression that I was attacking you personally
>> instead of promoting the idea that OSIS is not appropriate to set forth
>> as a standard f
Kahunapule Michael Johnson wrote:
First, please let me apologize. By the personal attacks in your message,
you may have gotten the impression that I was attacking you personally
instead of promoting the idea that OSIS is not appropriate to set forth
as a standard format for use in Bible translati
Hello, Chris!
First, please let me apologize. By the personal attacks in your message,
you may have gotten the impression that I was attacking you personally
instead of promoting the idea that OSIS is not appropriate to set forth
as a standard format for use in Bible translation and Scripture file
Chris Little wrote:
> Like any NEW technology, it requires that we do work. To that extent,
> it is more work than we would have had to do had we just stuck with
> GBF, ThML, etc. But I would rather move to OSIS alone than stick with
> those formats because OSIS can actually handle markup needs tha
Kahunapule Michael Johnson wrote:
Troy A. Griffitts wrote:
I disagree that OSIS has slowed down development here. It COULD
HAVE slowed down development here if we tried to actually work on our
osis2mod converter to handle a broader range of legal OSIS markup, but
up to now, we pretty much
Kahunapule Michael Johnson wrote:
Why Use OSIS When USFM and USFX Work Better?
Because OSIS is an open standard, available to all and open to the input
and contributions of all; USFM and USFX are not. Oh yeah, not to mention
OSIS is in most ways superior (i.e. works better than USFM or US
Troy A. Griffitts wrote:
> MPJ,
> Hello my friend. It's good to hear from you. It seems like
> 2/3rds of your issues with OSIS are having to do with . May I
> suggest patience to review what comes out of the last OSIS meeting
> back in December. We had a good hard look at practical uses of
Much deleted.
Troy A. Griffitts wrote:
How, in legal XML, do you markup multiple overlapping hierarchies like:
paragraph markers
We struggled with this and came up with what you suggest in you paper:
milestones. And I think we've tried our best to make the milestoning
syntax strai
MPJ,
Hello my friend. It's good to hear from you. It seems like 2/3rds of
your issues with OSIS are having to do with . May I suggest patience
to review what comes out of the last OSIS meeting back in December. We
had a good hard look at practical uses of , and believe me, your
concerns h
17 matches
Mail list logo
