[hts-users:02476] Re: Nature of hts_engine_API-1.03/HTS-2.1.1 format change for .pdf files
- Subject: [hts-users:02476] Re: Nature of hts_engine_API-1.03/HTS-2.1.1 format change for .pdf files
- From: Keiichiro Oura <uratec@xxxxxxxxxxxxxxx>
- Date: Tue, 18 May 2010 00:17:48 +0900
- Cc: uratec <uratec@xxxxxxxxxxxxxxx>
- Delivered-to: hts-users@xxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=7gb5xmR+XM7Rn1/bpvtWr9BRSKLcaJRHUkJrNs1roaQ=; b=JqYXTnL0vIXdTQ/PeDMZVZWFktrt3J8vf/XbjusDYsm30Xq2wiLUJuX/xBECsRPQQI 3ddCapEmO6OZe8eRxJN8Dc10EZc2QyspCpj/8fUDr+td4H2D9vt/DC0WgWidtLgPoG3d KcZoBsBZPKv0L2cL8MrdAOcdeBFhQtBuBB8v0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Rg9fOynbEiD8DVzi0NvkUx8XSgniHlQinWxsEuosFe52IQuYfLxwv46ba7iGbTi2X/ 7sBESzBX28Lh8va0hlWRmRKJ9mTGzZ38g1/go18IYxDeZ/qJ/a94Kg6sts/nHaLddkMG z/mQ77jVDJCmaPDQt639GC+PNlZuO9GHNGfwk=
Hi,
The old pdf files cannot be used in hts_engine API-1.03.
However, if you have mmf files and lists (HTS-2.1 format), pdf files
(hts_engine API-1.03 format) can be generated by using HHEd of
HTS-2.1.1.
I don't prepare the document of new file format.
Regards,
Keiichiro Oura
2010/5/17 Sacha Krstulovic <sacha@xxxxxxxxxxxxxxxxx>:
>
> Dear HTS and hts_engine developers;
>
> The hts_engine_API-1.03 changelog mentions:
>
> 2010-01-26 10:32 uratec
>
> * ChangeLog, lib/HTS_model.c: Change *.pdf file format in CM
> command
>
> I assume that CM command refers to a corresponding change
> in HHed for HTS-2.1.1.
>
> Before I upgrade to these versions, I would like
> to understand the following point:
>
> Is the .pdf format change backwards compatible, i.e.,
> is it still possible to use .pdf files generated by
> HTS-2.1 into hts_engine-1.03?
> Or is HTS-2.1.1 tied to hts_engine-1.03 and HTS<=2.1 tied to
> hts_engine<=1.02 regarding the format of the .pdf files?
>
> Is the nature of this format change documented somewhere?
> If not, could you please describe it briefly?
>
> Thanks and best regards;
>
> -*- Sacha K. -*-
>
> --
> Dr.Sacha Krstulovic - Research Engineer
> Toshiba Research Europe Limited
> Cambridge Research Laboratory
> Speech Technology Group
> 208 Science Park, Milton Road
> Cambridge CB4 0GZ - United Kingdom
> Tel: +44 1223 436 978
> Fax: +44 1223 436 909
> E-mail: sacha@xxxxxxxxxxxxxxxxx
>
> NOTE: The information in this email and any attachments may be
> confidential and/or legally privileged. This message may be read, copied
> and used only by the intended recipient. If you are not the intended
> recipient, please destroy this message, delete any copies held on your
> system and notify the sender immediately.
>
> Toshiba Research Europe Limited, registered in England and Wales (2519556).
> Registered Office: 208 Cambridge Science Park, Milton Road, Cambridge
> CB4 0GZ, England. Web: www.toshiba-europe.com/research/crl
>
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
- References
-
- [hts-users:02475] Nature of hts_engine_API-1.03/HTS-2.1.1 format change for .pdf files, Sacha Krstulovic