Enable prose-wrap
This commit is contained in:
parent
983beb89dc
commit
eb4f9402db
5 changed files with 57 additions and 31 deletions
|
@ -131,7 +131,8 @@
|
|||
|
||||
### Photo Editor
|
||||
|
||||
Check out our [blog](https://ente.io/blog/introducing-web-desktop-photo-editor/) to know about feature and functionalities.
|
||||
Check out our [blog](https://ente.io/blog/introducing-web-desktop-photo-editor/)
|
||||
to know about feature and functionalities.
|
||||
|
||||
## v1.6.47
|
||||
|
||||
|
@ -146,15 +147,19 @@ Check out our [blog](https://ente.io/blog/introducing-web-desktop-photo-editor/)
|
|||
|
||||
### Bug Fixes
|
||||
|
||||
- Fixes OOM crashes during file upload [#1379](https://github.com/ente-io/photos-web/pull/1379)
|
||||
- Fixes OOM crashes during file upload
|
||||
[#1379](https://github.com/ente-io/photos-web/pull/1379)
|
||||
|
||||
## v1.6.45
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
- Fixed app keeps reloading issue [#235](https://github.com/ente-io/photos-desktop/pull/235)
|
||||
- Fixed dng and arw preview issue [#1378](https://github.com/ente-io/photos-web/pull/1378)
|
||||
- Added view crash report option (help menu) for user to share electron crash report locally
|
||||
- Fixed app keeps reloading issue
|
||||
[#235](https://github.com/ente-io/photos-desktop/pull/235)
|
||||
- Fixed dng and arw preview issue
|
||||
[#1378](https://github.com/ente-io/photos-web/pull/1378)
|
||||
- Added view crash report option (help menu) for user to share electron crash
|
||||
report locally
|
||||
|
||||
## v1.6.44
|
||||
|
||||
|
@ -166,23 +171,28 @@ Check out our [blog](https://ente.io/blog/introducing-web-desktop-photo-editor/)
|
|||
|
||||
- #### Check for update and changelog option
|
||||
|
||||
Added options to check for update manually and a view changelog via the app menubar
|
||||
Added options to check for update manually and a view changelog via the app
|
||||
menubar
|
||||
|
||||
- #### Opt out of crash reporting
|
||||
|
||||
Added option to out of a crash reporting, it can accessed from the settings -> preferences -> disable crash reporting
|
||||
Added option to out of a crash reporting, it can accessed from the settings
|
||||
-> preferences -> disable crash reporting
|
||||
|
||||
- #### Type search
|
||||
|
||||
Added new search option to search files based on file type i.e, image, video, live-photo.
|
||||
Added new search option to search files based on file type i.e, image,
|
||||
video, live-photo.
|
||||
|
||||
- #### Manual Convert Button
|
||||
|
||||
In case the video is not playable, Now there is a convert button which can be used to trigger conversion of the video to supported format.
|
||||
In case the video is not playable, Now there is a convert button which can
|
||||
be used to trigger conversion of the video to supported format.
|
||||
|
||||
- #### File Download Progress
|
||||
|
||||
The file loader now also shows the exact percentage download progress, instead of just a simple loader.
|
||||
The file loader now also shows the exact percentage download progress,
|
||||
instead of just a simple loader.
|
||||
|
||||
- #### Bug fixes & other enhancements
|
||||
|
||||
|
@ -198,16 +208,19 @@ Check out our [blog](https://ente.io/blog/introducing-web-desktop-photo-editor/)
|
|||
|
||||
- #### Email verification
|
||||
|
||||
We have now made email verification optional, so you can sign in with just your email address and password, without waiting for a verification code.
|
||||
We have now made email verification optional, so you can sign in with just
|
||||
your email address and password, without waiting for a verification code.
|
||||
|
||||
You can opt in / out of email verification from Settings > Security.
|
||||
|
||||
- #### Download Album
|
||||
|
||||
You can now chose the download location for downloading albums. Along with that we have also added progress bar for album download.
|
||||
You can now chose the download location for downloading albums. Along with
|
||||
that we have also added progress bar for album download.
|
||||
|
||||
- #### Bug fixes & other enhancements
|
||||
|
||||
We have squashed a few pesky bugs that were reported by our community
|
||||
|
||||
If you would like to help us improve ente, come join the party @ ente.io/community!
|
||||
If you would like to help us improve ente, come join the party @
|
||||
ente.io/community!
|
||||
|
|
|
@ -2,8 +2,8 @@
|
|||
|
||||
The sweetness of Ente Photos, right on your computer. Linux, Windows and macOS.
|
||||
|
||||
You can [**download** a pre-built binary from
|
||||
releases](https://github.com/ente-io/photos-desktop/releases/latest).
|
||||
You can
|
||||
[**download** a pre-built binary from releases](https://github.com/ente-io/photos-desktop/releases/latest).
|
||||
|
||||
To know more about Ente, see [our main README](../README.md) or visit
|
||||
[ente.io](https://ente.io).
|
||||
|
|
|
@ -10,5 +10,5 @@ dependencies that are used by the Photos desktop app.
|
|||
### next-electron-server
|
||||
|
||||
This spins up a server for serving files using a protocol handler inside our
|
||||
Electron process. This allows us to directly use the output produced by `next
|
||||
build` for loading into our renderer process.
|
||||
Electron process. This allows us to directly use the output produced by
|
||||
`next build` for loading into our renderer process.
|
||||
|
|
|
@ -8,14 +8,14 @@ generated app thus consists of two separate processes - the _main_ process, and
|
|||
a _renderer_ process.
|
||||
|
||||
- The _main_ process is runs the embedded node. This process can deal with the
|
||||
host OS - it is conceptually like a `node` repl running on your machine. In our
|
||||
case, the TypeScript code (in the `src/` directory) gets transpiled by `tsc`
|
||||
into JavaScript in the `build/app/` directory, which gets bundled in the
|
||||
generated app's binary and is loaded by the node (main) process when the app
|
||||
starts.
|
||||
host OS - it is conceptually like a `node` repl running on your machine. In
|
||||
our case, the TypeScript code (in the `src/` directory) gets transpiled by
|
||||
`tsc` into JavaScript in the `build/app/` directory, which gets bundled in
|
||||
the generated app's binary and is loaded by the node (main) process when the
|
||||
app starts.
|
||||
|
||||
- The _renderer_ process is a regular web app that gets loaded into the embedded
|
||||
Chromium. When the main process starts, it creates a new "window" that shows
|
||||
this embedded Chromium. In our case, we build and bundle a static export of
|
||||
the [Photos web app](../web/README.md) in the generated app. This gets loaded
|
||||
by the embedded Chromium at runtime, acting as the app's UI.
|
||||
- The _renderer_ process is a regular web app that gets loaded into the
|
||||
embedded Chromium. When the main process starts, it creates a new "window"
|
||||
that shows this embedded Chromium. In our case, we build and bundle a static
|
||||
export of the [Photos web app](../web/README.md) in the generated app. This
|
||||
gets loaded by the embedded Chromium at runtime, acting as the app's UI.
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
# CLIP Byte Pair Encoding JavaScript Port
|
||||
|
||||
A JavaScript port of [OpenAI's CLIP byte-pair-encoding tokenizer](https://github.com/openai/CLIP/blob/3bee28119e6b28e75b82b811b87b56935314e6a5/clip/simple_tokenizer.py).
|
||||
A JavaScript port of
|
||||
[OpenAI's CLIP byte-pair-encoding tokenizer](https://github.com/openai/CLIP/blob/3bee28119e6b28e75b82b811b87b56935314e6a5/clip/simple_tokenizer.py).
|
||||
|
||||
```js
|
||||
import Tokenizer from "https://deno.land/x/clip_bpe@v0.0.6/mod.js";
|
||||
|
@ -18,10 +19,22 @@ t.encode("hello world!"); // [3306, 1002, 256]
|
|||
t.encodeForCLIP("hello world!"); // [49406,3306,1002,256,49407,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
|
||||
```
|
||||
|
||||
This encoder/decoder behaves differently to the the GPT-2/3 tokenizer (JavaScript version of that [here](https://github.com/latitudegames/GPT-3-Encoder)). For example, it doesn't preserve capital letters, as shown above.
|
||||
This encoder/decoder behaves differently to the the GPT-2/3 tokenizer
|
||||
(JavaScript version of that
|
||||
[here](https://github.com/latitudegames/GPT-3-Encoder)). For example, it doesn't
|
||||
preserve capital letters, as shown above.
|
||||
|
||||
The [Python version](https://github.com/openai/CLIP/blob/3bee28119e6b28e75b82b811b87b56935314e6a5/clip/simple_tokenizer.py) of this tokenizer uses the `ftfy` module to clean up the text before encoding it. I didn't include that module by default because currently the only version available in JavaScript is [this one](https://github.com/josephrocca/ftfy-pyodide), which requires importing a full Python runtime as a WebAssembly module. If you want the `ftfy` cleaning, just import it and clean your text with it before passing it to the `.encode()` method.
|
||||
The
|
||||
[Python version](https://github.com/openai/CLIP/blob/3bee28119e6b28e75b82b811b87b56935314e6a5/clip/simple_tokenizer.py)
|
||||
of this tokenizer uses the `ftfy` module to clean up the text before encoding
|
||||
it. I didn't include that module by default because currently the only version
|
||||
available in JavaScript is
|
||||
[this one](https://github.com/josephrocca/ftfy-pyodide), which requires
|
||||
importing a full Python runtime as a WebAssembly module. If you want the `ftfy`
|
||||
cleaning, just import it and clean your text with it before passing it to the
|
||||
`.encode()` method.
|
||||
|
||||
# License
|
||||
|
||||
To the extent that there is any original work in this repo, it is MIT Licensed, just like [openai/CLIP](https://github.com/openai/CLIP).
|
||||
To the extent that there is any original work in this repo, it is MIT Licensed,
|
||||
just like [openai/CLIP](https://github.com/openai/CLIP).
|
||||
|
|
Loading…
Add table
Reference in a new issue